Bug 837605
| Summary: | RHN Satellite raises traceback about ip6addr when doing hardware sync from new clients (RHEL 6.3) | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Jan Pazdziora <jpazdziora> |
| Component: | Server | Assignee: | Jan Pazdziora <jpazdziora> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Minar <mminar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 541 | CC: | chorn, cperry, ddevaraj, jhutar, jpazdziora, mkoci, mminar, presgas, xdmoon |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | spacewalk-backend-1.2.13-75 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 822435 | Environment: | |
| Last Closed: | 2012-07-23 15:33:20 UTC | Type: | Bug |
| 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: | 822435 | ||
| Bug Blocks: | 677498 | ||
|
Description
Jan Pazdziora
2012-07-04 11:26:17 UTC
Reading the code (no reproducer yet), this patch could help:
diff --git a/backend/server/rhnServer/server_hardware.py b/backend/server/rhnServer/server_hardware.py
index f23e2d6..f13c338 100644
--- a/backend/server/rhnServer/server_hardware.py
+++ b/backend/server/rhnServer/server_hardware.py
@@ -348,7 +348,7 @@ class CPUDevice(Device):
class NetworkInformation(Device):
def __init__(self, dict = None):
fields = ["hostname", "ipaddr"]
- mapping = { 'class' : None }
+ mapping = { 'class' : None, 'ip6addr' : None }
Device.__init__(self, "rhnServerNetwork", fields, dict, mapping)
# use our own sequence
self.sequence = "rhn_server_net_id_seq"
Fix in SATELLITE-5.4, d1c3eb5b30adc92255a246adb38c520c68734ef1. We are experiencing this issue. Isn't this due to the enhancement from rhn-client-tools on the recent 6.3 updat? https://bugzilla.redhat.com/show_bug.cgi?id=569790 https://bugzilla.redhat.com/show_bug.cgi?id=767679 I believe downgrading the rhn-client-tools seems to eliminate this. So, the more servers that get that update, the more satellite admins will get flooded with emails about the traceback. When is the estimated time this fix would come downstream? (In reply to comment #8) > We are experiencing this issue. Isn't this due to the enhancement from > rhn-client-tools on the recent 6.3 updat? > > https://bugzilla.redhat.com/show_bug.cgi?id=569790 > > https://bugzilla.redhat.com/show_bug.cgi?id=767679 > > I believe downgrading the rhn-client-tools seems to eliminate this. So, the > more servers that get that update, the more satellite admins will get > flooded with emails about the traceback. When is the estimated time this > fix would come downstream? The errata that this bug is associated too has 4 bugs to be QE tested before it can be released. We are trying to get this released as soon as possible, keeping within our normal regression test cycles before release of an errata. Please open a support ticket to track, we can provide guidance for time estimates via the support ticket system. Regards, Cliff Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-1108.html |