Description of problem:
rhn-client tools report HW info to rhnParent. But we currently send only IPv4 address and not IPv6 address.
We use python-ethtool to grab the information. We can either request IPv6 support in python-ethtool or do some workaround.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
We should also change in hardware.py in function change gethostbyname(gethostname()) to socket.getaddrinfo(gethostname()), but it does not contain simple value and we should somehow pick up the right value.
I do not consider this to be RHEL 6.0 material. We do not have working code, we do not even know if it would break the server side, if the server would be able to store the IPv6 data.
I'm going to move this to 6.1 instead of devel nacking this, so that we do not lose it from our radar.
Moving to space13.
Removing space13, this is not spacewalk bug.
Fixing blocks/depends on.
We seem to have fix in Spacewalk, in bug 655310. Devel ack.
Fix from bug 655310 require:
Requires: python-ethtool >= 0.4
We have two option:
a) flip this to RHEL7 BZ. But there will be rebase to current version, which will support it anyway.
b) rebase python-ethtool in RHEL6. Which is unlikely since this is not customer driven BZ.
Closing as WONTFIX.
Reopening as RHEL5 rebased to python-ethtool-0.6 in RHEL5.7 and in RHEL6.1
Setting devel ack for RHEL 6.3.
* 68fd40a (HEAD, client-rhel-6) 569790 - for scope on rhel5 do s/global/universe/
* ed0e024 743259 - RHEL5 now has python-ethtool 0.6 - simplify code
* 41b50c7 on el5 do not send IPv6 addresses
* f9a8024 655310 - replace gethostbyname by getaddrinfo
* 8e898b5 655310 - send IPv6 addresses to server
fixed in spacewalk.git by commit 1afa6549
cherrypicked as to satellite.git as 0d11ddbd0496ffcf446169531255da10acac7c99
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.