Details
-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.15
-
None
-
Important
-
No
-
False
-
Description
Description of problem:
[4.15 WMCO] Operator pod crashloopbackoff state
Version-Release number of selected component (if applicable):
4.15.0-0.nightly-2024-02-05-163411
How reproducible:
Always
Steps to Reproduce:
Steps : Install WMCO operator redhat edition from Operator hub Expected - Operator installation successfully and the pod is running in openshift-windows-machine-config-operator namespace
Actual results:
oc get podsNAME READY STATUS RESTARTS AGEwindows-machine-config-operator-66b77f94dd-bzwsk 0/1 CrashLoopBackOff 11 (114s ago) 33m[miyadav@miyadav ManualRun]$ oc logs windows-machine-config-operator-66b77f94dd-bzwsk{"level":"info","ts":"2024-02-06T06:35:30Z","logger":"version","msg":"operator","version":"10.15.0-ae56369"}{"level":"info","ts":"2024-02-06T06:35:30Z","logger":"version","msg":"go","version":"go1.20.12 linux/amd64"}{"level":"error","ts":"2024-02-06T06:35:30Z","logger":"setup","msg":"failed to validate required cluster configuration","error":"error validating network configuration: cluster is not configured for OVN hybrid networking","stacktrace":"main.main\n\t/remote-source/build/windows-machine-config-operator/cmd/operator/main.go:110\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:250"}
Expected results:
pod is up successfully
Additional info -
The cluster is using ovn networking , profile used for cluster installation - https://gitlab.cee.redhat.com/aosqe/flexy-templates/-/blob/master/functionality-testing/aos-4_15/ipi-on-aws/versioned-installer-wavelength_zone-ovn
