Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 100770 - up2date -update or any other options fails with Python error
up2date -update or any other options fails with Python error
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
Depends On:
  Show dependency treegraph
Reported: 2003-07-25 02:24 EDT by David M Walker
Modified: 2007-03-27 00:08 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-23 14:36:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David M Walker 2003-07-25 02:24:32 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

Description of problem:
One of our servers (and noticably not all of them besides the fact they all run
the same version) has started doing this:

# up2date --update
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

The is also true for other options such as up2date --force --download kernel,
which fails with exactly the same message

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run up2date --update


Actual Results:  As per log file above

Expected Results:  No crash error

Additional info:
Comment 1 David M Walker 2003-07-25 02:39:23 EDT
It turns out that (for reasons not needed here) the channel subscription on
rhn.redhat.com had been set to none, but a more graceful error would be nice
Comment 2 Adrian Likins 2004-08-20 17:11:37 EDT
indeed, current clients handle this better

Note You need to log in before you can comment on or make changes to this bug.