Red Hat Bugzilla – Bug 68527
up2date seems to complete but prints lots of junk and shows "Dummy Finish Page"
Last modified: 2015-01-07 18:57:32 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc2)
Description of problem:
15:10:18  bubo6:/root# up2date
/usr/share/rhn/up2date_client/gui.py:233: DeprecationWarning: use
color = self.druid.get_colormap().alloc(52232, 0, 0)
this is a deprecated call, please remove all use of it
Traceback (most recent call last):
File "/usr/share/rhn/up2date_client/gui.py", line 1014, in doInstallation
kernelsToInstall = up2date.installPackages(self.selectedPkgList,
File "/usr/share/rhn/up2date_client/up2date.py", line 470, in installPackages
rc = ts.run((1 << 10) , 0, rpmCallback, cfg.readEntry("storageDir"))
File "/usr/share/rhn/up2date_client/gui.py", line 976, in rpmCallback
i = (amount + 1.0) / total
ZeroDivisionError: float division
Finally, up2date displays Dummy Finish Page and says it should never get there.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. as per Message-ID: <00ab01c22819$43152d70$0301a8c0@bart>
From: "Mike Chambers" <firstname.lastname@example.org>
To: <email@example.com>, edit /etc/sysconfig/rhn/rhn_register and remove the
s from https and then run up2date-config and change the URL's to http instead of
2. run up2date from command line.
3. results in errors shown in description.
4. without doing step 1, up2date has bombed every time with no updates at all.
Actual Results: as described. got 52 packages updated.
Expected Results: no errors.
In Limbo-II (up2date-2.9.30):
The "Dimmy Finish Page" problem is still there: the "All finished" page has a
"forward" button and pressing it shows the "Dummy Finish page" that is not
supposed to be reached.
The "ZeroDivisionError: float division" is a separate bug and I beleieve was fixed.
totalProgress.update warnings are still there.
dummy page is still there. not exactly sure why glade doesnt
want to cooperate... will investigate.
The rest should be fixed in 2.9.39 at least