Bug 146044
Summary: | IndexError: list index out of range | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Graham Leggett <minfrin> |
Component: | up2date | Assignee: | Pradeep Kilambi <pkilambi> |
Status: | CLOSED WONTFIX | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | benl, tsanders, vgaikwad |
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: | 2008-02-28 17:06: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
Graham Leggett
2005-01-24 21:43:41 UTC
I also see the same error in up2date-4.4.67-3 at a slightly different location Traceback (most recent call last): File "/usr/sbin/rhnreg_ks", line 357, in ? File "/usr/sbin/rhnreg_ks", line 331, in main if serialnumber: File "/usr/share/rhn/up2date_client/rhnreg.py", line 391, in sendSerialNumber s = rpcServer.getServer() File "/usr/share/rhn/up2date_client/rpcServer.py", line 186, in getServer File "/usr/share/rhn/up2date_client/rpcServer.py", line 104, in server return self.serverurl IndexError: list index out of range It happens when I run up2date on any package and is the result of server load. /etc/sysconfig/rhn/up2date just has one server listed in *erverURL= vlad, this something you are seeing at GS? this may be difficult to reproduce since its load related. tried a couple of ways against our hosted/sat servers but as Mike mentioned its kinda hard to reproduce this load issue. Do you still have the box you reproduced this on? and could I play on it a little bit? Also this probably should be aligned to 4.6 and not 500. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was previously evaluated by Red Hat Product Management for inclusion in the current Red Hat Enterprise Linux release, but Red Hat was unable to resolve it in time. This request will be reviewed for a future Red Hat Enterprise Linux release. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Could you please elaborate of the server load required to reproduce this bug? What exactly is the trigger for the bug? Is it simply the server not responding? or is it a failure to repond to a specific request? From what i recall the server wasn't responding for the getRetryServer call.. so looks like the server load itself.. unfortunately I was not able to reproduce this issue. Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request. |