Bug 1238671

Summary: bridge0: changed to bridge0@NONE in ip addr output
Product: Red Hat Enterprise Linux 7 Reporter: Lubomir Rintel <lrintel>
Component: iprouteAssignee: Pavel Šimerda (pavlix) <psimerda>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: jbenc, lrintel
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-07 15:52:53 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:

Description Lubomir Rintel 2015-07-02 11:38:58 UTC
This change made it into 7.2 kernel: http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/ip/ipaddress.c?id=ccdcbf35f120c754660b3b3f48fa67cc950a6407

However, the change breaks NetworkManager test suite and possibly anything else that scrapes the ip output.

Please investigate the possibility of coping with the kernel change and retaining the format from ip without change.

Comment 1 Jiri Benc 2015-07-02 11:50:30 UTC
The @NONE output should be fixed in the kernel. I filed bug 1238672 for that.

We now return iface@link for more interfaces than before, though. That's a correct behavior and anything scraping ip output needs to be aware of this format. The format is not new, it's just returned for more interfaces now; one example is veth interfaces.

Comment 3 Pavel Šimerda (pavlix) 2015-07-02 12:02:52 UTC
When we talked on IRC, I assumed we are talking about a regression in the iproute package. If the regression is in kernel, and as jbenc says it should be fixed in the kernel, should we even consider it for iproute? Is upstream considering it at all?

Comment 4 Lubomir Rintel 2015-07-02 12:06:02 UTC
I don't think so.
I wasn't sure if this was getting fixed in kernel at the time I reported this.
Feel free to close this.

Comment 5 Pavel Šimerda (pavlix) 2015-07-07 15:52:53 UTC
Thanks for your feedback!