We want to start using our new SMT server and the first server (SLES11 SP2) that was added as a client appears to be missing updates that were showing as “Recommended” from the Novell Update servers.
Before running the “clientSetup4SMT.sh” script I examined if any update were listed as Recommended.
Online Update reported:
I also examined this SLES server list of repositories and made certain that all those repositories were made available on our SMT.
Everything appears to have gone well except that Online Update only reports “ksh” as a recommended update.
I somehow missed the following repositories so I added them to the SMT. I was focussing more on selecting all our SLES10 and OES2 repositories.
Once these were added to SMT, I re-registered from the SLES11SP2 client and found that new repositories were listed on that server.
Online Update still only shows “ksh”.
Before I start deploying this SMT for use by our SLES10, OES2, OES11 servers, I really need to trust that I’ll be getting all updates.
Please let me know what I’ve missed.
I checked the “yast2-wagon” update from another SLES11SP2 server and see that we have 220.127.116.11.7.1 but that another version should be recommended for 18.104.22.168-0.5.1
I checked the “audit” update from another SLES11SP2 server and see that we have 1.8-0.28.1 but that another version should be recommended for 1.8-0.30.1
Please let me know what I need to do on our new SMT server or on the SLES11SP2 client to have these updates showing as recommended.
I’d appreciate any suggestions to avoid having our clients miss updates when using internal SMT.
Thanks for any help,