Bug 678986 - flushing secondary device does not work
Summary: flushing secondary device does not work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iproute
Version: 6.0
Hardware: All
OS: All
medium
medium
Target Milestone: rc
: 6.0
Assignee: Petr Šabata
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-21 08:16 UTC by Takuma Umeya
Modified: 2018-11-14 14:48 UTC (History)
2 users (show)

Fixed In Version: iproute-2.6.32-15.el6
Doc Type: Bug Fix
Doc Text:
Previously, attempting to flush a secondary device with "ip secondary" would fail. This issue has now been corrected and secondary devices are flushed as expected.
Clone Of:
Environment:
Last Closed: 2011-05-19 14:23:33 UTC
Target Upstream Version:


Attachments (Terms of Use)
Flush secondary IP addresses correctly (4.13 KB, patch)
2011-02-22 09:47 UTC, Petr Šabata
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0757 0 normal SHIPPED_LIVE iproute bug fix and enhancement update 2011-05-18 18:08:52 UTC

Description Takuma Umeya 2011-02-21 08:16:23 UTC
Description of problem:
Flushing secondary device does not work. ip command implements the use of secondary option. When this option is used together with flush option the command does not work as expected. 

Version-Release number of selected component (if applicable):
iputils-20071127-13.el6

How reproducible:
Always 

Steps to Reproduce:
1. 
# ip addr show dev br0
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 84:2b:2b:67:87:70 brd ff:ff:ff:ff:ff:ff
inet 10.38.11.10/24 brd 10.38.11.255 scope global br0
inet 10.38.11.144/24 scope global secondary br0
inet 10.38.11.139/24 scope global secondary br0
inet6 fe80::862b:2bff:fe67:8770/64 scope link
valid_lft forever preferred_lft forever

2. 
# ip addr show dev br0 secondary
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 84:2b:2b:67:87:70 brd ff:ff:ff:ff:ff:ff
inet 10.38.11.144/24 scope global secondary br0
inet 10.38.11.139/24 scope global secondary br0

3. 
# ip addr flush dev br0 secondary

4. 
# ip addr show dev br0
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 84:2b:2b:67:87:70 brd ff:ff:ff:ff:ff:ff
inet 10.38.11.10/24 brd 10.38.11.255 scope global br0
inet 10.38.11.144/24 scope global secondary br0
inet 10.38.11.139/24 scope global secondary br0
inet6 fe80::862b:2bff:fe67:8770/64 scope link
valid_lft forever preferred_lft forever
  
Actual results:
The secondary device won't get flushed. 

Expected results:
The secondary device should get flushed. 

Additional info:
An engineer has found that the part of the patch related to this is committed through the following git: 
3bc1c4f29777171b484d36abf673667e3729202b

He has cherry-picked the part of it and confirmed it resolves the issue.

Comment 2 Petr Šabata 2011-02-22 09:47:31 UTC
Created attachment 480087 [details]
Flush secondary IP addresses correctly

Changed the referenced patch to apply & work with EL6 iproute2.
This patch fixes the issue.

Comment 4 Petr Šabata 2011-02-22 17:50:38 UTC
Fixed in CVS tag iproute-2.6.32-15.el6

Comment 7 Laura Bailey 2011-05-11 07:36:40 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, attempting to flush a secondary device with "ip secondary" would fail. This issue has now been corrected and secondary devices are flushed as expected.

Comment 8 errata-xmlrpc 2011-05-19 14:23:33 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0757.html


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