Hide Forgot
Description of problem: after add bond slave, ip link show type bond_slave do not show anything Version-Release number of selected component (if applicable): iproute-3.10.0-74.el7 How reproducible: everytime Steps to Reproduce: 1. # ip link set p5p1 master bond0 2. # ip link show type bond_slave 3. Actual results: show nothing Expected results: show slaves Additional info: need backport commit 03ac85b708168c57ce6ec32dfa5aa850fbf2c4ee Author: Phil Sutter <phil> Date: Thu Jun 30 16:47:02 2016 +0200 ip-address: constify match_link_kind arg Since the function won't ever change the data 'kind' is pointing at, it can sanely be made const. Fixes: e0513807f6dbb ("ip-address: Support filtering by slave type, too") Suggested-by: Stephen Hemminger <shemming> Signed-off-by: Phil Sutter <phil>
Hi Hangbin, The requested functionality is indeed not available in RHEL7 iproute. The missing patch though is this one: commit e0513807f6dbbd4631fdbb27f0bd6bbce138e8cd Author: Phil Sutter <phil> Date: Tue Jun 28 15:07:16 2016 +0200 ip-address: Support filtering by slave type, too This patch allows to query all interfaces enslaved to a bridge or bond using the following syntax: | ip addr show type bridge_slave Filtering has to be done in userspace since the kernel does not support filtering on IFLA_INFO_SLAVE_KIND. Functionality introduced in this patch is not fully complete since it does not allow to match on type and slave type at the same time, but it doesn't prevent implementing a dedicated slave_type match, either. Signed-off-by: Phil Sutter <phil>
(In reply to Phil Sutter from comment #1) > Hi Hangbin, > > The requested functionality is indeed not available in RHEL7 iproute. The > missing patch though is this one: > > commit e0513807f6dbbd4631fdbb27f0bd6bbce138e8cd > Author: Phil Sutter <phil> > Date: Tue Jun 28 15:07:16 2016 +0200 ah, no wonder... I thought we already backported this patch. Do we have a internal git repo for iproute2? So I can check what patch we have backported. Thanks Hanagbin
(In reply to Hangbin Liu from comment #2) > (In reply to Phil Sutter from comment #1) > > Hi Hangbin, > > > > The requested functionality is indeed not available in RHEL7 iproute. The > > missing patch though is this one: > > > > commit e0513807f6dbbd4631fdbb27f0bd6bbce138e8cd > > Author: Phil Sutter <phil> > > Date: Tue Jun 28 15:07:16 2016 +0200 > > ah, no wonder... I thought we already backported this patch. Do we have a > internal git repo for iproute2? So I can check what patch we have backported. Yes, indeed there is: http://git.engineering.redhat.com/git/users/psutter/iproute2.git/ Branch rhel7.3 is what you are looking for. I duplicated the kernel git infrastructure as much as possible, so dist-git releases are created from this git in a semi-automatic way. Cheers, Phil
(In reply to Phil Sutter from comment #3) > Yes, indeed there is: > > http://git.engineering.redhat.com/git/users/psutter/iproute2.git/ > > Branch rhel7.3 is what you are looking for. I duplicated the kernel git > infrastructure as much as possible, so dist-git releases are created from > this git in a semi-automatic way. Cool, thanks
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/RHBA-2017:2171