Bug 115385
Summary: | rhn_check (4.2.*) won't update multiple errata against RHN Proxy | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Todd Warner <taw> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED ERRATA | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.0 | CC: | gpryzby, rhn-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-26 23:23:20 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: | |||
Bug Depends On: | |||
Bug Blocks: | 110950, 124335 |
Description
Todd Warner
2004-02-11 20:14:07 UTC
Figured out that this is an object referencing issue. I.e., the token is a global object that's reference is retained in a several classes (HttpGetServer for example). When a new login occurs mid process the new token (a dictionary) is reassigned to the object (new reference). The classes retain a reference to the old object. So... therein lies the disconnect. The correct methodology to fix this is to always fetch the object with the up2dateAuth.getLoginInfo() function. For now, I have simply fixed the reference problem. But... relying on references being retained is fragile. getLoginInfo() is really the right answer. See bug 124335 for TEST PLAN NOTE: fails against all versions of RHN Proxy NOTE2: un-privatizing this bug so folks don't create duplicates. *** Bug 125810 has been marked as a duplicate of this bug. *** The fix seems to work just dandy. Blocking on the backport to be passed: bug 124335 Looks good on the front end. There are some backend issues that need to be resolved (see bug: 124335), but there is another bug already open for these issues. The fix works. |