-
Bug
-
Resolution: Unresolved
-
Major
-
4.19
-
None
-
Important
-
Yes
-
Proposed
-
False
-
Description of problem:
Version-Release number of selected component (if applicable):
In 4.19, whereabouts-reconciler pods are CrashLoopBackOff after creating additionalNetworks
How reproducible:
Always
Steps to Reproduce:
1. After a OCP cluster up, oc edit networks.operator.openshift.io cluster
additionalNetworks:
- name: whereabouts-shim
namespace: default
type: Raw
rawCNIConfig: |-
{
"cniVersion": "0.3.0",
"type": "bridge",
"name": "cnitest0",
"ipam": {
"type": "whereabouts",
"subnet": "192.0.2.0/24"
}
}
Actual results:
whereabouts-reconciler pods are created and CrashLoopBackOff in 4.19
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.19.0-0.nightly-2025-03-04-213423 True False 3h22m Error while reconciling 4.19.0-0.nightly-2025-03-04-213423: the cluster operator network is degraded $ oc get pod | grep whereabouts-reconciler whereabouts-reconciler-dd5w8 0/1 CrashLoopBackOff 14 (5m5s ago) 51m whereabouts-reconciler-lbtmz 0/1 CrashLoopBackOff 14 (5m4s ago) 51m whereabouts-reconciler-m6qx5 0/1 CrashLoopBackOff 14 (4m47s ago) 51m whereabouts-reconciler-njkhm 0/1 CrashLoopBackOff 14 (4m54s ago) 51m whereabouts-reconciler-pg5hr 0/1 CrashLoopBackOff 14 (5m5s ago) 51m whereabouts-reconciler-q24fw 0/1 CrashLoopBackOff 14 (4m53s ago) 51m
Expected results:
whereabouts-reconciler pods are created and Running in 4.18
$ oc get pod | grep whereabouts-reconciler whereabouts-reconciler-689jq 1/1 Running 0 33s whereabouts-reconciler-8nzcv 1/1 Running 0 33s whereabouts-reconciler-cr8qp 1/1 Running 0 33s whereabouts-reconciler-qqv6k 1/1 Running 0 33s whereabouts-reconciler-w48w7 1/1 Running 0 33s whereabouts-reconciler-xxl2f 1/1 Running 0 33s $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.18.0-0.nightly-2025-03-05-050145 True False 40m Cluster version is 4.18.0-0.nightly-2025-03-05-050145
Additional info:
This is a 4.19 regression bug.
