Cluster update known issues¶
This section lists the cluster update known issues with workarounds for the Mirantis OpenStack for Kubernetes release 22.3.
 The ‘ironic-conductor’ Pod fails after the management cluster upgrade¶
After the Container Cloud management cluster upgrade from 2.19.0 to 2.20.0,
ironic-conductor Pod gets stuck in the
CrashLoopBackOff state. The
issue occurs due to the race condition between the
ironic-conductor-http containers of the
ironic-conductor Pod that try
ca-bundle.pem simultaneously but from different users.
As a workaround, run the following command:
kubectl -n openstack exec -t <failedPodName> -c ironic-conductor-http -- chown 42424:42424 /certs/ca-bundle.pem
 Cluster update failure after OpenStack controller node replacement¶
After an OpenStack controller node replacement, the
octavia-create-resources job does not restart and the Octavia Health
Manager Pod on the new node cannot find its port in the Kubernetes secret. As a
result, MOSK cluster update may fail.
After adding the new OpenStack controller node but before the update process
starts, manually restart the
kubectl -n osh-system exec <OSCTL_POD> -- osctl-job-rerun octavia-create-resources openstack
 MetalLB speaker fails to announce the LB IP for the Ingress service¶
After updating the MOSK cluster, MetalLB speaker may fail to announce the Load Balancer (LB) IP address for the OpenStack Ingress service. As a result, the OpenStack Ingress service is not accessible using its LB IP address.
The issue may occur if the MetalLB speaker
nodeSelector selects not all
the nodes selected by
nodeSelector of the OpenStack Ingress service.
The issue may arise and disappear when a new MetalLB speaker is being selected by the MetalLB Controller to announce the LB IP address.
The issue occurs since MOSK 22.2 after
externalTrafficPolicy was set to
local for the OpenStack Ingress
Select from the following options:
clusterfor the OpenStack Ingress service.
This option is preferable in the following cases:
If not all cluster nodes have connection to the external network
If the connection to the external network cannot be established
If network configuration changes are not desired
If network configuration is allowed and if you require the
Wire the external network to all cluster nodes where the OpenStack Ingress service Pods are running.
Configure IP addresses in the external network on the nodes and change the default routes on the nodes.
nodeSelectorof MetalLB speaker to match
nodeSelectorof the OpenStack Ingress service.
 Ceph health is in ‘HEALTH_WARN’ state after managed cluster update¶
After updating the MOSK cluster, Ceph health is in
HEALTH_WARN state with the
SLOW_OPS health message.
The workaround is to restart the affected Ceph Monitors.