Red Hat Bugzilla – Bug 111863
up2date failure after upgrading up2date components
Last modified: 2007-11-30 17:06:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
Description of problem:
After an initial installation of AS2.1, we tried up2date. Of course,
we got the SSL error, so we downloaded up2date-22.214.171.124-1.2.1AS and
the related components (rhn_register, ..._gnome, et al). Now, after an
"up2date -p", any attempt to do an update crashes with a python traceback:
[root@srv01 root]# up2date -u
Traceback (innermost last):
File "/usr/sbin/up2date", line 781, in ?
File "/usr/sbin/up2date", line 569, in main
pkgNames, fullUpdate, dryRun = dry_run))
File "/usr/sbin/up2date", line 724, in batchRun
File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 57, in run
File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 89, in
File "/usr/share/rhn/up2date_client/packageList.py", line 85, in run
File "/usr/share/rhn/up2date_client/packageList.py", line 109, in
for p in obsoletePackages:
TypeError: loop over non-sequence
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Do a fresh AS2.1 install
2. Download and "rpm -Fvh" the 126.96.36.199-1.2.1AS components
3. "up2date -p"
4. "up2date -u".....kerPOW!
Actual Results: The traceback in the description.
Expected Results: I'd expect an updated system. This certainly seems
poor design. You can't update an AS2.1 system without up2date, and
up2date is itself flakey as all get out.
make sure the boxes that show this error have
a channel assigned to them. Common cause of
missing channels is lack of proper RHN
entitlements for the channels in questions.
newer clients also handle this case