Bug 1656074

Summary: os-net-config don't restart vlan when a change append on bond (OSP-14)
Product: Red Hat OpenStack Reporter: Bob Fournier <bfournie>
Component: os-net-configAssignee: Harald Jensås <hjensas>
Status: CLOSED ERRATA QA Contact: Alistair Tonner <atonner>
Severity: high Docs Contact:
Priority: high    
Version: 14.0 (Rocky)CC: atonner, bfournie, ccopello, cylopez, hbrock, hjensas, jslagle, mburns, sasha
Target Milestone: z1Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: os-net-config-9.2.1-0.20190117181408.8e9242b.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1655765 Environment:
Last Closed: 2019-03-18 13:03:24 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: 1654987, 1655765    
Bug Blocks:    

Comment 4 Alistair Tonner 2019-03-08 11:56:58 UTC 
VERIFIED


core_puddle_version
2019-03-05.1


rpm -q os-net-config
os-net-config-9.2.1-0.20190117181409.el7ost.noarch




os-net-config -c /tmp/config.json -v
[2019/03/08 11:49:46 AM] [INFO] Using config file at: /tmp/config.json
[2019/03/08 11:49:46 AM] [INFO] Ifcfg net config provider created.
[2019/03/08 11:49:46 AM] [INFO] Not using any mapping file.
[2019/03/08 11:49:46 AM] [INFO] Finding active nics
[2019/03/08 11:49:46 AM] [INFO] br-int is not an active nic
[2019/03/08 11:49:46 AM] [INFO] ovs-system is not an active nic
[2019/03/08 11:49:46 AM] [INFO] eth1 is an embedded active nic
[2019/03/08 11:49:46 AM] [INFO] eth0 is an embedded active nic
[2019/03/08 11:49:46 AM] [INFO] eth2 is an embedded active nic
[2019/03/08 11:49:46 AM] [INFO] eth3 is an embedded active nic
[2019/03/08 11:49:46 AM] [INFO] lo is not an active nic
[2019/03/08 11:49:46 AM] [INFO] bonding_masters is not an active nic
[2019/03/08 11:49:46 AM] [INFO] docker0 is not an active nic
[2019/03/08 11:49:46 AM] [INFO] br-ex is not an active nic
[2019/03/08 11:49:46 AM] [INFO] bond0 is not an active nic
[2019/03/08 11:49:46 AM] [INFO] br-isolated is not an active nic
[2019/03/08 11:49:46 AM] [INFO] vlan50 is not an active nic
[2019/03/08 11:49:46 AM] [INFO] vlan30 is not an active nic
[2019/03/08 11:49:46 AM] [INFO] vlan20 is not an active nic
[2019/03/08 11:49:46 AM] [INFO] No DPDK mapping available in path (/var/lib/os-net-config/dpdk_mapping.yaml)
[2019/03/08 11:49:46 AM] [INFO] Active nics are ['eth0', 'eth1', 'eth2', 'eth3']
[2019/03/08 11:49:46 AM] [INFO] nic4 mapped to: eth3
[2019/03/08 11:49:46 AM] [INFO] nic3 mapped to: eth2
[2019/03/08 11:49:46 AM] [INFO] nic2 mapped to: eth1
[2019/03/08 11:49:46 AM] [INFO] nic1 mapped to: eth0
[2019/03/08 11:49:46 AM] [INFO] adding linux bond: bond0
[2019/03/08 11:49:46 AM] [INFO] adding custom route for interface: bond0
[2019/03/08 11:49:46 AM] [INFO] adding interface: eth3
[2019/03/08 11:49:46 AM] [INFO] adding vlan: vlan610
[2019/03/08 11:49:46 AM] [INFO] adding custom route for interface: vlan610
[2019/03/08 11:49:46 AM] [INFO] adding vlan: vlan611
[2019/03/08 11:49:46 AM] [INFO] adding custom route for interface: vlan611
[2019/03/08 11:49:46 AM] [INFO] adding vlan: vlan612
[2019/03/08 11:49:46 AM] [INFO] adding custom route for interface: vlan612
[2019/03/08 11:49:46 AM] [INFO] applying network configs...
[2019/03/08 11:49:46 AM] [INFO] running ifdown on interface: vlan612
[2019/03/08 11:49:46 AM] [INFO] running ifdown on interface: vlan611
[2019/03/08 11:49:46 AM] [INFO] running ifdown on interface: vlan610
[2019/03/08 11:49:46 AM] [INFO] running ifdown on interface: eth3
[2019/03/08 11:49:46 AM] [INFO] running ifdown on interface: bond0
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/route-vlan612
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/route-vlan610
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/route-vlan611
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/route-bond0
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-bond0
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-vlan610
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-vlan611
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-vlan612
[2019/03/08 11:49:46 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-eth3
[2019/03/08 11:49:46 AM] [INFO] running ifup on interface: eth3
[2019/03/08 11:49:47 AM] [INFO] running ifup on interface: bond0
[2019/03/08 11:49:51 AM] [INFO] running ifup on interface: vlan612
[2019/03/08 11:49:55 AM] [INFO] running ifup on interface: vlan611
[2019/03/08 11:49:59 AM] [INFO] running ifup on interface: vlan610


ip r
default via 192.168.24.1 dev eth0
172.17.1.0/24 dev vlan20 proto kernel scope link src 172.17.1.24
172.17.2.0/24 dev vlan50 proto kernel scope link src 172.17.2.28
172.17.3.0/24 dev vlan30 proto kernel scope link src 172.17.3.32
172.20.1.0/26 dev vlan610 proto kernel scope link src 172.20.1.10
172.20.1.64/26 dev vlan611 proto kernel scope link src 172.20.1.70
172.20.1.192/26 dev vlan612 proto kernel scope link src 172.20.1.200
172.31.0.0/24 dev docker0 proto kernel scope link src 172.31.0.1
172.31.170.0/26 dev bond0 proto kernel scope link src 172.31.170.27
172.33.9.0/26 via 172.20.1.62 dev vlan610                             <<---scope
172.33.18.0/24 via 172.20.1.126 dev vlan611                           <<---scope
192.168.24.0/24 dev eth0 proto kernel scope link src 192.168.24.14


grep miimon /tmp/config.json 
            "bonding_options": "mode=1 miimon=111",

[root@compute-1 tmp]# sed -i s/miimon=111/miimon=120/g  /tmp/config.json
[root@compute-1 tmp]# grep miimon /tmp/config.json 
            "bonding_options": "mode=1 miimon=120",

os-net-config -c /tmp/config.json -v
[2019/03/08 11:53:39 AM] [INFO] Using config file at: /tmp/config.json
[2019/03/08 11:53:39 AM] [INFO] Ifcfg net config provider created.
[2019/03/08 11:53:39 AM] [INFO] Not using any mapping file.
[2019/03/08 11:53:40 AM] [INFO] Finding active nics
[2019/03/08 11:53:40 AM] [INFO] br-int is not an active nic
[2019/03/08 11:53:40 AM] [INFO] ovs-system is not an active nic
[2019/03/08 11:53:40 AM] [INFO] eth1 is an embedded active nic
[2019/03/08 11:53:40 AM] [INFO] eth0 is an embedded active nic
[2019/03/08 11:53:40 AM] [INFO] eth2 is an embedded active nic
[2019/03/08 11:53:40 AM] [INFO] eth3 is an embedded active nic
[2019/03/08 11:53:40 AM] [INFO] lo is not an active nic
[2019/03/08 11:53:40 AM] [INFO] bonding_masters is not an active nic
[2019/03/08 11:53:40 AM] [INFO] docker0 is not an active nic
[2019/03/08 11:53:40 AM] [INFO] br-ex is not an active nic
[2019/03/08 11:53:40 AM] [INFO] bond0 is not an active nic
[2019/03/08 11:53:40 AM] [INFO] br-isolated is not an active nic
[2019/03/08 11:53:40 AM] [INFO] vlan612 is not an active nic
[2019/03/08 11:53:40 AM] [INFO] vlan611 is not an active nic
[2019/03/08 11:53:40 AM] [INFO] vlan610 is not an active nic
[2019/03/08 11:53:40 AM] [INFO] vlan50 is not an active nic
[2019/03/08 11:53:40 AM] [INFO] vlan30 is not an active nic
[2019/03/08 11:53:40 AM] [INFO] vlan20 is not an active nic
[2019/03/08 11:53:40 AM] [INFO] No DPDK mapping available in path (/var/lib/os-net-config/dpdk_mapping.yaml)
[2019/03/08 11:53:40 AM] [INFO] Active nics are ['eth0', 'eth1', 'eth2', 'eth3']
[2019/03/08 11:53:40 AM] [INFO] nic4 mapped to: eth3
[2019/03/08 11:53:40 AM] [INFO] nic3 mapped to: eth2
[2019/03/08 11:53:40 AM] [INFO] nic2 mapped to: eth1
[2019/03/08 11:53:40 AM] [INFO] nic1 mapped to: eth0
[2019/03/08 11:53:40 AM] [INFO] adding linux bond: bond0
[2019/03/08 11:53:40 AM] [INFO] adding custom route for interface: bond0
[2019/03/08 11:53:40 AM] [INFO] adding interface: eth3
[2019/03/08 11:53:40 AM] [INFO] adding vlan: vlan610
[2019/03/08 11:53:40 AM] [INFO] adding custom route for interface: vlan610
[2019/03/08 11:53:40 AM] [INFO] adding vlan: vlan611
[2019/03/08 11:53:40 AM] [INFO] adding custom route for interface: vlan611
[2019/03/08 11:53:40 AM] [INFO] adding vlan: vlan612
[2019/03/08 11:53:40 AM] [INFO] adding custom route for interface: vlan612
[2019/03/08 11:53:40 AM] [INFO] applying network configs...
[2019/03/08 11:53:40 AM] [INFO] No changes required for interface: eth3
[2019/03/08 11:53:40 AM] [INFO] running ifdown on interface: vlan612
[2019/03/08 11:53:40 AM] [INFO] running ifdown on interface: vlan611
[2019/03/08 11:53:40 AM] [INFO] running ifdown on interface: vlan610
[2019/03/08 11:53:40 AM] [INFO] running ifdown on interface: eth3
[2019/03/08 11:53:40 AM] [INFO] running ifdown on interface: bond0
[2019/03/08 11:53:41 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-vlan610
[2019/03/08 11:53:41 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-vlan611
[2019/03/08 11:53:41 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-vlan612
[2019/03/08 11:53:41 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-bond0
[2019/03/08 11:53:41 AM] [INFO] running ifup on interface: eth3
[2019/03/08 11:53:41 AM] [INFO] running ifup on interface: bond0
[2019/03/08 11:53:45 AM] [INFO] running ifup on interface: vlan612
[2019/03/08 11:53:49 AM] [INFO] running ifup on interface: vlan611
[2019/03/08 11:53:54 AM] [INFO] running ifup on interface: vlan610


ip r
default via 192.168.24.1 dev eth0

172.17.1.0/24 dev vlan20 proto kernel scope link src 172.17.1.24
172.17.2.0/24 dev vlan50 proto kernel scope link src 172.17.2.28
172.17.3.0/24 dev vlan30 proto kernel scope link src 172.17.3.32
172.20.1.0/26 dev vlan610 proto kernel scope link src 172.20.1.10
172.20.1.64/26 dev vlan611 proto kernel scope link src 172.20.1.70
172.20.1.192/26 dev vlan612 proto kernel scope link src 172.20.1.200
172.31.0.0/24 dev docker0 proto kernel scope link src 172.31.0.1
172.31.170.0/26 dev bond0 proto kernel scope link src 172.31.170.27
172.33.9.0/26 via 172.20.1.62 dev vlan610                              <<--- VERIFIED
172.33.18.0/24 via 172.20.1.126 dev vlan611                            <<--- VERIFIED
192.168.24.0/24 dev eth0 proto kernel scope link src 192.168.24.14
Comment 8 errata-xmlrpc 2019-03-18 13:03:24 UTC 
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-2019:0446