On Mon, Sep 10, 2018 at 09:19:41AM -0000, bugproxy wrote: > So either i suspect one of the two issues here
> 1)nmcli was internally handling this in case of other distros. i.e > deactivated the vlan, when bond is deactivated and activate the vlan , > when bond is activated. > OR > 2)network kernel underlying module takes care of these notifications > between bond and vlan. I suspected this because, as i did not see any log > updates with respect to nmcli tool for automatically deactivating and > activating VLAN It would be good for us to be able to isolate which of these two cases it is, since if there is a bug with the kernel driver, that is definitely in scope for us to ensure we fix. To establish that this is a kernel bug, we would need to see a reproducer for it in your existing environment that does not depend on nmcli, but is instead reproducible using low-level iproute2 commands. -- 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
