Re: Reg. nmstate issue with OVS interfaces.
by Gris Ge
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_requ...
Is it?
>
>
> 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
2 years, 8 months
Re: Reg. nmstate issue with OVS interfaces.
by Gris Ge
On Mon, Jun 22, 2020 at 11:24:51AM +0000, Vishal Deep Ajmera wrote:
> Hi,
>
> As requested please find attached logs collected after enabling
> tracing in network-manager. I have created one OVS bridge 'bridge0'
> and 3 interfaces. I see that randomly only one interface gets the IP
> and others don't after every reboot of the system.
Hi Vishal,
Thanks for the logs.
We are actively debugging this issue:
* When OS boot up, `autoconnect-slave=True` will conflict with
`autoconnect=True`
* The slaves manually activation will conflict with master
activation.
Will let you know once fix been found.
Best regards!
--
Gris Ge
2 years, 9 months
Reg. nmstate issue with OVS interfaces.
by Vishal Deep Ajmera
Hi NM Team,
We are currently using Network Manager to manage OVS interfaces and facing
one issue with nmstate.
Attached is the yaml file we are using to setup OVS bridge and interfaces.
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.
Here are the software versions we are using.
Host machine is running SLES (SUSE linux).
#nmcli --version
nmcli tool, version 1.24.0
#nmstatectl --version
0.3.0
As a workaround we tried by removing the line "autoconnect-slaves=1" from
the .nmconnection files and tried the reboot again.
This time, the issue did not occur and we could see that the OVS interface
is configured properly with assigned IP address.
Have you seen similar issue before? Any idea on how this is connected to
"autoconnect-slaves" flag?
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"?
Warm Regards,
Vishal Ajmera
2 years, 9 months