-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14
-
Important
-
No
-
Approved
-
False
-
Description of problem:
From CLBO ovnkube-node logs: Upgrade hack: Timed out waiting for the remote ovnkube-controller to be ready even after 5 minutes, err : context deadline exceeded, unable to fetch node-subnet annotation for node ip-10-0-133-201.us-east-2.compute.internal: err, could not find "k8s.ovn.org/node-subnets" annotation ovnkube-controller not ready implies the absence of node-subnets annotation CNO upgrade stuck at DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" rollout is not making progress - last change 2023-08-30T10:06:44Z
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-08-11-055332
How reproducible:
Always
Steps to Reproduce:
1.Install OCP cluster with RHCOS and win nodes on 4.13 2.Perform upgrade to 4.14 3.
Actual results:
Upgrades failed on CNO
Expected results:
Upgrade should pass
Additional info:
must-gather: http://shell.lab.bos.redhat.com/~anusaxen/must-gather.local.1473221474492991466/
- clones
-
OCPBUGS-18352 winc upgrades are failing from 4.13 -> 4.14 due to remote ovnkube-controller is not ready
- Closed
- depends on
-
OCPBUGS-18352 winc upgrades are failing from 4.13 -> 4.14 due to remote ovnkube-controller is not ready
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update