Description of problem: From 4.3 to 4.4 we changed app=ovnkube-master to name=ovnkube-master in https://github.com/openshift/cluster-network-operator/pull/435 https://github.com/openshift/cluster-network-operator/pull/419 OVN is TP in 4.3, so upgrade is unsupported, but this change will break automation scripts. Tracking bug for CI automation failures. Version-Release number of selected component (if applicable): 4.4 How reproducible: Always Steps to Reproduce: 1. upgrade OVN 4.3 cluster to 4.4 2. 3. Actual results: Error while updating operator configuration: could not apply (apps/v1, Kind=DaemonSet) openshift-ovn-kubernetes/ovnkube-master: could not update object (apps/v1, Kind=DaemonSet) openshift-ovn-kubernetes/ovnkube-master: DaemonSet.apps "ovnkube-master" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app":"ovnkube-master"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable Expected results: upgrade succeeds Additional info:
Looks like this was fixed in https://github.com/openshift/cluster-network-operator/pull/483
OVN 4.3 to 4.4 upgrade completed successfully with 4.3.0-0.nightly-2020-02-27-054508 to 4.4.0-0.nightly-2020-02-27-070700
*** Bug 1809997 has been marked as a duplicate of this bug. ***
now this issue only happen on 4.3.3 to latest 4.3 nightly build and 4.4 version. do we have customer is using 4.3.3 for OVN since 4.3.3 is TP I guess? if no. I guess we do not need to do upgrade for it.
Upgrades from 4.3 to 4.4 are not supported... the only supported customer will be doing a reinstall and will not be upgrading.
*** Bug 1823483 has been marked as a duplicate of this bug. ***