Bug 1111152
| Summary: | sosreport ifconfig infinband whinges | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jeremy Harris <jeharris> | ||||
| Component: | net-tools | Assignee: | Michal Ruprich <mruprich> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.5 | CC: | agk, bmr, gavin, sbradley, thozza | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-09-05 14:47:14 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: | |||||||
| Attachments: |
|
||||||
Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes. Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly. Ifconfig is obsolete! For replacement check ip. Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes. Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly. Based on comment #2 ifconfig is not going to be ever to show the correct information. If the "ip addr" output shows the correct information then this should be closed as notabug. Having painful clutter is not a bug? If looking at ifconfig output causes you pain stop looking at it. In all seriousness we cannot address the limitations of ifconfig for modern interface types in sos. We can arrange to discard ifconfig stderr in future which would eliminate the messages from captured data, although, this is at the risk of possibly discarding other more serious errors (and there is nothing stopping users from grepping this out today if they wish to or experience pain at the sight of these messages ;). Also looking at the data attached in comment #0 it looks like there may be an ifconfig bug that's causing a 2nd copy of the message to be mixed in with the infiniband interface details: ib0 Link encap:InfiniBand HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:2044 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:256 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) ib1 Link encap:InfiniBand HWaddr 80:00:00:48:FE:80:00:00:00:00:00:0Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes. Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly. Ifconfig is obsolete! For replacement check ip. Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes. Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly. Ifconfig is obsolete! For replacement check ip. 0:00:00:00:00:00:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:2044 Metric:1 RX packets:0 errors The message appears to have been appended following the HWaddr field value. This doesn't seem right but again this is an ifconfig problem - not something that we can solve in sos. Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com |
Created attachment 910353 [details] ifconfig file from sosreport Description of problem: The "ifconfig" file in sosreport is cluttered with "Ifconfig is obsolete" whinges Version-Release number of selected component (if applicable): Red Hat Enterprise Linux Server release 6.5 (Santiago) How reproducible: Probably only when there are IB interfaces Steps to Reproduce: 1. Read sosreport Additional info: See attached ifconfig file