Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1692099 - [libnm][bond] Activating/Committing an active bond restarts its link (up-down-up)
Summary: [libnm][bond] Activating/Committing an active bond restarts its link (up-down...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: sushil kulkarni
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-24 10:10 UTC by Edward Haas
Modified: 2019-03-25 07:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Edward Haas 2019-03-24 10:10:32 UTC
Description of problem:
When using libnm and an existing Bond profile is updated with the same configuration through `commit changes`, followed by the profile `activate`, the Bond interface flickers (up-down-up).
Such a behaviour causes traffic disruption for the system and best avoided.

This has been confirmed to occur using `nmcli` as well.

Version-Release number of selected component (if applicable):
1.12.0-8.el7_6

How reproducible:
100%

Steps to Reproduce:
Using nmcli:
1. Create a bond with one slave.
2. Monitor the bond using ip-monitor: `ip monitor link dev <bond name>`
3. Re-activate the bond once again (no changes to the profile): `nmcli con up <bond name>`

Actual results:
Bond link state flickers from UP to DOWN and UP again.

Expected results:


Additional info:
When just attaching the slave, without mentioning the bond at all, only an `up` event is seen, which is considered a good behaviour.

ip-monitor events when issuing `nmcli con up bond88`:
```
49: bond88: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 0a:ab:28:e9:49:ca brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 0a:ab:28:e9:49:ca brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 0a:ab:28:e9:49:ca brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
49: bond88: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 6a:e9:66:3b:a7:3b brd ff:ff:ff:ff:ff:ff
```

Comment 2 Edward Haas 2019-03-25 07:30:06 UTC
This is probably not related to bonds only, but a general point on any interface type.


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