Bug 1042804

Summary:	Inconsistent detailed link information between "ip link" and "ip monitor link"
Product:	[Fedora] Fedora	Reporter:	Antoni Segura Puimedon <asegurap>
Component:	iproute	Assignee:	Pavel Šimerda (pavlix) <psimerda>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	20	CC:	bazulay, danken, ebenes, jpopelka, rvokal, twoerner
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1042799	Environment:
Last Closed:	2015-06-30 00:46:23 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:
Bug Blocks:	1042802

Description Antoni Segura Puimedon 2013-12-13 12:23:13 UTC

+++ This bug was initially created as a clone of Bug #1042799 +++

Description of problem:
In the output of "ip -d -o link show" and "ip -d -o monitor link" vlan and
macvlan devices are reported with the following form:
"device name" + "@" + "device name of the underlying device".

Since it is perfectly legal for another device to include symbols in their
names, e.g., "@", it is perfectly possible to have a dummy device called:
p1p3.13@p1p3

and a vlan device called p1p3.13 that is being reported as
p1p3.13@p1p3

In the output of "ip -d -o link show" this is disambiguable thanks to the fact
that dummies, vlans and macvlans have their type shown in the final segment:

    21: p1p3.13@p1p3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN \    link/ether 00:10:18:e1:6c:f4 brd ff:ff:ff:ff:ff:ff\    vlan id 13 <REORDER_HDR>
    23: p1p3.13@p1p3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN \    link/ether 82:17:ed:f9:e8:f3 brd ff:ff:ff:ff:ff:ff\    dummy 

However, the output of "ip -d -o monitor link" doesn't include the type
information for any device (not even for just vlanned and dummy types like
"ip -d -o link show" does). E.g.:
    23: p1p3.13@p1p3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN \    link/ether c2:01:5c:db:bd:39 brd ff:ff:ff:ff:ff:ff
    21: p1p3.13@p1p3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN \    link/ether 00:10:18:e1:6c:f4 brd ff:ff:ff:ff:ff:ff

Without a priori knowledge (having executed before a detailed link show and
keeping a database by interface index) there is no way to tell that the former
is a dummy and the latter is the vlan.

Version-Release number of selected component (if applicable): all


How reproducible: 100%


Steps to Reproduce:
1. start the monitor "ip -d -o monitor link"
2. Create vlan 13 over a nic (for example named p1p3)
3. Create a dummy called "p1p3.13@p1p3"
4. Check the detailed link monitor output

Actual results:
    23: p1p3.13@p1p3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN \    link/ether c2:01:5c:db:bd:39 brd ff:ff:ff:ff:ff:ff
    21: p1p3.13@p1p3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN \    link/ether 00:10:18:e1:6c:f4 brd ff:ff:ff:ff:ff:ff


Expected results:
    23: p1p3.13@p1p3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN \    link/ether c2:01:5c:db:bd:39 brd ff:ff:ff:ff:ff:ff\    dummy 
    21: p1p3.13@p1p3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN \    link/ether 00:10:18:e1:6c:f4 brd ff:ff:ff:ff:ff:ff\    vlan id 13 <REORDER_HDR>

Comment 1 Fedora Admin XMLRPC Client 2014-08-20 08:54:07 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-05-29 09:58:57 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-30 00:46:23 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.