Tested on 4.10.0-0.ci.test-2022-05-16-010951-ci-ln-i2647it-latest vSphere UPI static and DHCP May 16 01:33:10.721860 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + nmcli c load /etc/NetworkManager/system-connections/ovs-if-br-ex.nmconnection May 16 01:33:10.736806 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + nmcli c mod ovs-if-br-ex ipv4.route-metric 48 ipv6.route-metric 48 May 16 01:33:10.756771 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + echo 'Loaded new ovs-if-br-ex connection file: /etc/NetworkManager/system-connections/ovs-if-br-ex.nmconnection' May 16 01:33:10.756968 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: Loaded new ovs-if-br-ex connection file: /etc/NetworkManager/system-connections/ovs-if-br-ex.nmconnection May 16 01:33:10.757038 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + configure_driver_options ens192 May 16 01:33:10.757139 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + intf=ens192 May 16 01:33:10.757198 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + '[' '!' -f /sys/class/net/ens192/device/uevent ']' May 16 01:33:10.757782 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: ++ cat /sys/class/net/ens192/device/uevent May 16 01:33:10.757834 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: ++ grep DRIVER May 16 01:33:10.758041 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: ++ awk -F = '{print $2}' May 16 01:33:11.157188 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + ip route show May 16 01:33:11.157518 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: default via 172.31.248.1 dev br-ex proto static metric 48 May 16 01:33:11.157649 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: default via 192.168.60.1 dev ens224 proto dhcp metric 100 May 16 01:33:11.157649 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: default via 192.168.61.1 dev ens256 proto dhcp metric 101 May 16 01:33:11.157649 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: 172.31.248.0/23 dev br-ex proto kernel scope link src 172.31.248.112 metric 48 May 16 01:33:11.157649 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: 192.168.60.0/25 dev ens224 proto kernel scope link src 192.168.60.73 metric 100 May 16 01:33:11.157649 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: 192.168.61.0/25 dev ens256 proto kernel scope link src 192.168.61.123 metric 101 May 16 01:33:11.157792 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + ip -6 route show May 16 01:33:11.158572 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: ::1 dev lo proto kernel metric 256 pref medium May 16 01:33:11.158619 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: fe80::/64 dev ens224 proto kernel metric 100 pref medium May 16 01:33:11.158619 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: fe80::/64 dev ens256 proto kernel metric 101 pref medium May 16 01:33:11.158805 rbrattai-o410v72m-q78qr-compute-1 configure-ovs.sh[1402]: + exit 0 May 16 01:33:11.159224 rbrattai-o410v72m-q78qr-compute-1 systemd[1]: ovs-configuration.service: Succeeded.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.10.16 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:4754