Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ovs-configuration.service via DHCP (Error: failed to modify connection.slave-type) #2115

Open
pavel-veber opened this issue Feb 14, 2025 · 1 comment

Comments

@pavel-veber
Copy link

Describe the bug

When installing OKD, everything is fine, the cluster is working, the nodes are Ready.
After reboot, the network is not working(ssh only) and there is an error in ovs-configuration.service:

 configure-ovs.sh[1752]: + nmcli c add type ovs-port conn.interface ens18 master br-ex con-name ovs-port-phys0 connection.autoconnect-slaves 1 connection.autoconnect no
 configure-ovs.sh[1917]: Error: failed to modify connection.slave-type: 'ovs-interface' not among [bond, bridge, ovs-bridge, ovs-port, team, vrf].
 configure-ovs.sh[1752]: ++ handle_exit
 configure-ovs.sh[1752]: ++ e=2

Version

OKD: 4.15.0-0.okd-2024-03-10-010116 bare-metal UPI hosts with OVNKubernetes.
Network: One ethernet port.
Boot: via iPXE (ip=dhcp).

How reproducible

In my case, it is reproduced frequently, about 99%.
And it rarely happens that it is necessary to load.

Log bundle

master-1_first_boot.log

master-1_after_reboot.log

However there is workaround is remove MN keyfile
[root@master-1 ~]# rm -v /etc/NetworkManager/system-connections/ovs-if-br-ex-108d42c4-d0b9-4064-a40f-117e35fa1ef5.nmconnection && systemctl reboot

@pavel-veber
Copy link
Author

The features that I noticed:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant