vlan lost route during a stack update

Issue

From a compute already deployed with NIC in a BOND with VLAN on top.

[root@cpt-0-m630v4 ~]# ip r
default via 192.168.151.1 dev vlan1421 <-----------------
192.168.1.2 via 192.168.151.1 dev vlan1421 <-----------------
192.168.1.5 via 192.168.155.1 dev vhost0
192.168.2.2 via 192.168.151.1 dev vlan1421 <-----------------
192.168.2.5 via 192.168.155.1 dev vhost0
169.254.0.1 dev vhost0 proto 109 scope link
169.254.169.254 via 192.168.150.2 dev bond0
192.168.145.0/27 via 192.168.155.1 dev vhost0
192.168.150.0/26 dev bond0 proto kernel scope link src 192.168.150.21
192.168.151.0/27 dev vlan1421 proto kernel scope link src 192.168.151.20
192.168.152.0/27 dev vlan1422 proto kernel scope link src 192.168.152.20
192.168.154.0/27 dev vlan1424 proto kernel scope link src 192.168.154.20
192.168.155.0/27 dev vhost0 proto kernel scope link src 192.168.155.20

Make a change and call os-net-config

[root@cpt-0-m630v4 ~]# os-net-config -c /etc/os-net-config/config.json -d 
[2018/11/30 09:28:46 AM] [INFO] No changes required for linux bond: bond1
[2018/11/30 09:28:46 AM] [INFO] running ifdown on interface: em1
[2018/11/30 09:28:46 AM] [DEBUG] Running cmd (subprocess): /sbin/ifdown em1
[2018/11/30 09:28:47 AM] [DEBUG] CMD "/sbin/ifdown em1" returned: 0 in 0.291s
[2018/11/30 09:28:47 AM] [INFO] running ifdown on interface: p2p1
[2018/11/30 09:28:47 AM] [DEBUG] Running cmd (subprocess): /sbin/ifdown p2p1
[2018/11/30 09:28:47 AM] [DEBUG] CMD "/sbin/ifdown p2p1" returned: 0 in 0.258s
[2018/11/30 09:28:47 AM] [INFO] running ifdown on interface: bond0
[2018/11/30 09:28:47 AM] [DEBUG] Running cmd (subprocess): /sbin/ifdown bond0
[2018/11/30 09:28:47 AM] [DEBUG] CMD "/sbin/ifdown bond0" returned: 0 in 0.409s
[2018/11/30 09:28:47 AM] [INFO] Writing config /etc/sysconfig/network-scripts/route6-bond0
[2018/11/30 09:28:47 AM] [INFO] Writing config /etc/sysconfig/network-scripts/route-bond0
[2018/11/30 09:28:47 AM] [INFO] Writing config /etc/sysconfig/network-scripts/ifcfg-bond0
[2018/11/30 09:28:47 AM] [INFO] running ifup on interface: em1
[2018/11/30 09:28:47 AM] [DEBUG] Running cmd (subprocess): /sbin/ifup em1
[2018/11/30 09:28:48 AM] [DEBUG] CMD "/sbin/ifup em1" returned: 0 in 0.265s
[2018/11/30 09:28:48 AM] [INFO] running ifup on interface: p2p1
[2018/11/30 09:28:48 AM] [DEBUG] Running cmd (subprocess): /sbin/ifup p2p1
[2018/11/30 09:28:48 AM] [DEBUG] CMD "/sbin/ifup p2p1" returned: 0 in 0.268s
[2018/11/30 09:28:48 AM] [INFO] running ifup on interface: bond0
[2018/11/30 09:28:48 AM] [DEBUG] Running cmd (subprocess): /sbin/ifup bond0
[2018/11/30 09:28:52 AM] [DEBUG] CMD "/sbin/ifup bond0" returned: 0 in 4.321s

Here our route on vlan1421 is lost because when bond0 is down, all VLAN based routes on bond0 are lost. VLANs are M-DOWN.

[root@cpt-0-m630v4 ~]# ip r
192.168.1.5 via 192.168.155.1 dev vhost0
192.168.2.5 via 192.168.155.1 dev vhost0
169.254.0.1 dev vhost0 proto 109 scope link
169.254.169.254 via 192.168.150.2 dev bond0
192.168.145.0/27 via 192.168.155.1 dev vhost0
192.168.150.0/26 dev bond0 proto kernel scope link src 192.168.150.21
192.168.151.0/27 dev vlan1421 proto kernel scope link src 192.168.151.20
192.168.152.0/27 dev vlan1422 proto kernel scope link src 192.168.152.20
192.168.154.0/27 dev vlan1424 proto kernel scope link src 192.168.154.20
192.168.155.0/27 dev vhost0 proto kernel scope link src 192.168.155.20