Hide Forgot
Description of problem: Deploy upi-on-vsphere cluster with ovn network enabled, installation is failed at the step of waiting for bootstrap completed. Checked on master node, found that service ovs-configuration was started failed, and br-ex link is not up. Attached gather log for details. Version-Release number of selected component (if applicable): 4.7.0-0.nightly-2021-03-10-202622 How reproducible: Always on upi-on-vsphere, didn't find on ipi-on-vsphere Steps to Reproduce: 1. Deploy upi-on-vsphere + ovn network enabled 2. Installation is failed 3. Actual results: Fail to deploy cluster Expected results: Cluster is deployed successfully Additional info:
> it seems we are missing a plugin > > sh-4.4# cat /etc/NetworkManager/NetworkManager.conf NetworkManager ships an empty configuration file (or better: with only comments). This is intended. > In /etc/NetworkManager/NetworkManager.conf > [main] > #plugins=ifcfg-rh > [...] > based on the above I think we have to un comment the plugins line and restart NetworkManager The default on rhel-8 is already "plugins=ifcfg-rh" (which is the same as "plugins=ifcfg-rh,keyile") (while on Fedora 33+ it is "plugins=keyfile,ifcfg-rh"). The setting in NetworkManager.conf is commented out to show what the default is. Uncommenting it, has little effect. Except, if would have an effect if you had /usr/lib/NetworkManager/conf.d/10-some.conf > [main] > plugins=something then having /etc/NetworkManager/NetworkManager.conf > [main] > plugins=ifcfg would make a difference. Run `sudo NetworkManager --print-config` to see the configuration.
This fix updated the configfile for you https://github.com/openshift/machine-config-operator/commit/a2815aa4993954ec6f30785c8c0a1d0a79109a4b and it was merged to 4.7
The above fix was merged a few days ago into 4.7: https://github.com/openshift/machine-config-operator/pull/2426 So it makes sense it suddenly started working for you. But you probably need the cloned-mac-address fix as well.
*** Bug 1942006 has been marked as a duplicate of this bug. ***
*** Bug 1949351 has been marked as a duplicate of this bug. ***