Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1471236 - networking: please run ip address with -d
networking: please run ip address with -d
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Pavel Moravec
Jakub Heger
https://github.com/sosreport/sos/pull...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-14 15:07 EDT by Jiri Benc
Modified: 2018-04-10 14:03 EDT (History)
8 users (show)

See Also:
Fixed In Version: sos-3.5-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 14:01:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0963 None None None 2018-04-10 14:03 EDT

  None (edit)
Description Jiri Benc 2017-07-14 15:07:56 EDT
While working on bug 1469790, the provided sosreport did not contain output of

ip -d address

That's unfortunate, as without the -d option, ip address output is missing a lot of highly useful information for bonding, tunnels, etc.

Please include the -d option. It's not necessary to have both "ip a" and "ip -d a", just adding the option unconditionally would be okay.
Comment 2 Jiri Benc 2017-07-14 15:42:02 EDT
It seems to be impossible to determine bond slave status from the information gathered by RHEL7 sosreport. The only other place beside "ip -d a" is /sys/class/net/*/bonding_slave/state but that one is not gathered, either.
Comment 3 Pavel Moravec 2017-07-24 04:37:15 EDT
ACK, just deferring to 7.5 due to the stage of 7.4 release.
Comment 4 Pavel Moravec 2017-11-02 11:15:03 EDT
Fixed via sos 3.5 rebase.
Comment 10 errata-xmlrpc 2018-04-10 14:01:47 EDT
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.

https://access.redhat.com/errata/RHEA-2018:0963

Note You need to log in before you can comment on or make changes to this bug.