openstack-baremetal-operator-controller-manager pod crashes after OpenShift upgrade

Solution In Progress - Updated -

Issue

  • Upgrading the OpenShift cluster from version 4.16.10 to 4.16.12 caused openstack-baremetal-operator-controller-manager pod to be in CrashLoopBackOff status with the following error in the "manager" container log:
Reconciler error {"controller": "openstackbaremetalset", "controllerGroup": "baremetal.openstack.org", "controllerKind": "OpenStackBaremetalSet", "OpenStackBaremetalSet": {"name":"openstack1-data-plane-hci","namespace":"openstack"}, "namespace": "openstack", "name": "openstack1-data-plane-hci", "reconcileID": "3e038cca-f532-48e4-b4ea-9e249fb68b1a", "error": "Internal error occurred: failed calling webhook \"mopenstackprovisionserver.kb.io\": failed to call webhook: Post \"https://openstack-baremetal-operator-controller-manager-service.openstack-operators.svc:443/mutate-baremetal-openstack-org-v1beta1-openstackprovisionserver?timeout=10s\": no endpoints available for service \"openstack-baremetal-operator-controller-manager-service\""}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.6/pkg/internal/controller/controller.go:329
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.6/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.6/pkg/internal/controller/controller.go:227

Environment

  • Red Hat Openstack Services on Openshift 18.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content