-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
4.13.z, 4.12.z
-
Important
-
No
-
False
-
This is a clone of issue OCPBUGS-22293. The following is the description of the original issue:
—
Description of problem:
Upgrading from 4.13.5 to 4.13.17 fails at network operator upgrade
Version-Release number of selected component (if applicable):
How reproducible:
Not sure since we only had one cluster on 4.13.5.
Steps to Reproduce:
1. Have a cluster on version 4.13.5 witn ovn kubernetes 2. Set desired update image to quay.io/openshift-release-dev/ocp-release@sha256:c1f2fa2170c02869484a4e049132128e216a363634d38abf292eef181e93b692 3. Wait until it reaches network operator
Actual results:
Error message: Error while updating operator configuration: could not apply (apps/v1, Kind=DaemonSet) openshift-ovn-kubernetes/ovnkube-master: failed to apply / update (apps/v1, Kind=DaemonSet) openshift-ovn-kubernetes/ovnkube-master: DaemonSet.apps "ovnkube-master" is invalid: [spec.template.spec.containers[1].lifecycle.preStop: Required value: must specify a handler type, spec.template.spec.containers[3].lifecycle.preStop: Required value: must specify a handler type]
Expected results:
Network operator upgrades successfully
Additional info:
Since I'm not able to attach files please gather all required debug data from https://access.redhat.com/support/cases/#/case/03645170
- duplicates
-
-
- Closed
-
- links to
