Red Hat Bugzilla – Bug 66254
self.setArrorCursor() typo in up2date
Last modified: 2015-01-07 18:57:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513
Description of problem:
Traceback (innermost last):
File "/usr/share/rhn/up2date_client/gui.py", line 832, in doInstallation
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I presume that "self.setArrorCursor()" really ought to be "self.setArrowCursor()".
I believe everything worked and install was successful. I got the latest kernel
and grub was updated (but not lilo, sigh). however, the hourglass cursor is
still present on the gui which gives the impression that it crashed prior to
forgot to mention. the gui is left with only the "cancel" button enabled. the
back and next buttons are not enabled. which furthers the impression that the
packages were not fully installed. (but I think they were.)
% rpm -V kernel-source-2.4.9-34 kernel-doc-2.4.9-34 kernel-debug-2.4.9-34
so yes, I think everything was installed fine.
This typo is in the CommunicationError exception handler. The last log message
I see says "Removing packages from package profile: [...]" so the
CommunicationError would have been raised in remoteDelPackages. Could this be
related to the fact that the server disabled free service at about that time?
Is there any way to "grandfather" currently running up2date sessions when that
happens? Anyway, it looks like the packages installed successfully, but RHN
could not be notified of this fact.
This (the typo) should be fixed in the next versions.
When the servers start throttling live users, it is
done at login time. Existing up2date sessions that
have valid authentication tokens should be fine
for the duration of the token time.
It possible that a connnection was possibly
dropped at this time do to time outs. Generally
servers only get throttled when we are 100% bandwitdth
utilization, so it's possible.
I presume this can be closed.
up2date-2.8.39-1.7.2 has this fixed