Description of problem: Downgrade(4.6.0-0.nightly-2020-10-05-234751 -> 4.5.0-0.nightly-2020-10-05-204452) stuck on the network operator. Version-Release number of selected component (if applicable): 4.6.0-0.nightly-2020-10-05-234751 4.5.0-0.nightly-2020-10-05-204452 How reproducible: Always Steps to Reproduce: 1.Install 4.6 cluster 2.Downgrade 4.6 to 4.5 cluster version 3. Actual results: Downgrade stuck on the network operator Expected results: Downgrade should successful. Additional info: $ oc logs ovs-6xdx4 ovsdb-server: /var/run/openvswitch/ovsdb-server.pid: pidfile check failed (No such process), aborting Starting ovsdb-server ... failed!
In 4.6 we don't need to do anything. We need to handle it on the downgrade.
This is not something we can fix in 4.6. We have the 4.5.z PR to handle the case open (https://github.com/openshift/cluster-network-operator/pull/830), and we have a bz open against the MCO to get the ovs disabled on the host. Note, that only PR https://github.com/openshift/cluster-network-operator/pull/830 is needed to allow downgrade.