You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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
The text was updated successfully, but these errors were encountered: