------- Comment From [email protected] 2018-09-07 05:39 EDT------- I agree that we need to switch to netplan, but that is currently not feasible approach for us. We will keep you updated once we have anything concrete on it.
We expect nmcli also to work as we get the rpm from ubuntu repo. While i was investigating the below case between RHEL and Ubuntu, i noticed the below behaviour. Test case : 1)Create bond 2)Create vlan 3)Deactivate bond #routes for both bond and vlan gets deleted## Hence vlan also gets deactivated 4)Activate bond #Routes get created for bond and not for vlan. ## Hence vlan continues to be in deactivated state? Where in case of RHEL, the route for vlan also was created in step 4, hence the vlan was in activated state. I monitored the system logs during above execution, i did not notice nmcli doing any explicit activation/deactivation logs for vlan when bond was deactivated or activated. So with this i suspect, its underlying kernel taking care of some sort of notification events which is black box to me. Could you please help us inspect on same lines and review the case? What is the expected behaviour with netplan for the above test case? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790098/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
