Bug 66254
Summary: | self.setArrorCursor() typo in up2date | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jim Wright <jwright> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED ERRATA | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | gafton, jdalbec, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-10-26 02:47:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jim Wright
2002-06-06 19:56:48 UTC
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 kernel-2.4.9-34 kernel-headers-2.4.9-34 S.5....T /boot/kernel.h-2.4.9 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 |