On Mon, Jun 22, 2020 at 01:55:35PM +0800, Gris Ge wrote:

On Mon, Jun 22, 2020 at 04:45:00AM +0000, Vishal Deep Ajmera wrote:

...

Hi NM Team,

The problem we are facing is that initially when the OVS bridge and interface is not present, the Network Manager is able to properly create them and configures the IP address on the interface. After this, when we reboot the machine we see that the interface is not configured by NetworkManager. It fails with error "dependency-failed". Unfortunately no other error is seen in the journalctl output. Also attached is the .nmconnection file generated by nmstate cli.

Hi Vishal Deep Ajmera,

I failed to reproduce in my VM.

Can you create `/etc/NetworkManager/conf.d/debug.conf` with these contents:

[logging] level=TRACE domains=ALL

And then provide output of `sudo journalctl -t NetworkManager -b0`?

...

As a workaround we tried by removing the line "autoconnect-slaves=1" from the .nmconnection files and tried the reboot again.

...

Have you seen similar issue before? Any idea on how this is connected to "autoconnect-slaves" flag?

Hi Beniamino,

This sounds like the old problem of NetworkManager: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_request...

Is it?

Yes, there is a race condition if you set autoconnect-slaves=1 on the master and also set the slaves to autoconnect. I'm working on fixing it; the merge request you linked had to be reverted because it introduced regressions.

To workaround this bug, nmstate could avoid setting autoconnect-slaves, since the slaves are already configured to autoconnect.

Beniamino

...

Also, we were not able to find any parameter which can be set in the input yaml file which can disable this flag.

Is there something available or the default is always "1"?

Nmstate currently does not support disable this option yet.

And I am afraid we cannot add the support, cause: * For complex nested bridge/vlan/bond setup, we need to trust NetworkManager do the slave activation in the correct order.

* The slave activation order will impact the MAC address choosing,
  if nmstate do the slave activation manually, the MAC address of
  master(bridge/bond) might be different after OS reboot.

But I will work with you to find out the root cause and get it fixed in NetworkManager.

The next actions would be:

* Vishal collects NetworkManager trace/debug logs.
* Beniamino review this email and/or the logs, then feedback.

Best regards.

-- Gris Ge