After upgrading a bunch of SLES 10 servers to SP1, some (but not all) servers were now getting 401 Login Failed errors when doing a rug refresh (or any rug actions) from novell’s update servers. On some servers, deleting the update sources in Yast2 and reregistering via the customer center solved the issues, but on some it did not. (The issue only occurred on servers I upgraded to SP1, not where I did an install from SP1 sources.)
On the problematic ones:
Those update sources were listed as ZYPP sources, not NU. (I was letting yast create them via synchronizing with zenworks)
I had to:
remove old services:
rug sd SLES10-SP1-Online
rug sd SLES10-SP1-Updates
Add the new one (with the type specified, or it errored):
rug sa -t nu https://nu.novell.com
Subscribe to the new catalogs:
rug ca
Sub’d? | Name |
Service
——-+——————————————————–+——————————————————-
Yes | SUSE-Linux-Enterprise-Server-i386-10-0-20070605-044231 |
SUSE-Linux-Enterprise-Server-i386-10-0-20070605-044231
| SLES10-SP1-Online |
https://nu.novell.com
| SLES10-SP1-Updates |
https://nu.novell.com
| SLE10-SP1-Debuginfo-Updates |
https://nu.novell.com
#rug sub SLES10-SP1-Online
Subscribed to ‘SLES10-SP1-Online’
#rug sub SLES10-SP1-Updates
Subscribed to ‘SLES10-SP1-Updates’
rug worked then, but I still had 401 errors in Yast2 (when going to
online update, customer center, or installation sources)
To resolve them, I then had to remove the update sources in Yast2,
re-run the Novell customer center configuration, and then things seem OK.