-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.13.z
-
None
-
Important
-
No
-
SDN Sprint 237
-
1
-
Proposed
-
False
-
-
N/A
-
Release Note Not Required
Description of problem:
The cluster network operator crashes in an IBM ROKS with the following error: 2023-06-07T12:21:37.402285420-05:00 stderr F I0607 17:21:37.402108 1 log.go:198] Failed to render: failed to render multus admission controller manifests: failed to render file bindata/network/multus-admission-controller/admission-controller.yaml: failed to render manifest bindata/network/multus-admission-controller/admission-controller.yaml: template: bindata/network/multus-admission-controller/admission-controller.yaml:199:12: executing "bindata/network/multus-admission-controller/admission-controller.yaml" at <.HCPNodeSelector>: map has no entry for key "HCPNodeSelector"
Version-Release number of selected component (if applicable):
4.13.1
How reproducible:
Always
Steps to Reproduce:
1. Run a ROKS cluster with OCP 4.13.1 2. 3.
Actual results:
CNO crashes
Expected results:
CNO functions normally
Additional info:
ROKS worked ok with 4.13.0 This change was introduced in 4.13.1: https://github.com/openshift/cluster-network-operator/pull/1802
- blocks
-
OCPBUGS-14871 Cluster network operator in IBM ROKS is crashlooping
- Closed
- is cloned by
-
OCPBUGS-14871 Cluster network operator in IBM ROKS is crashlooping
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update