In Red Hat OpenStack Services on OpenShift (RHOSO) 18.0.3, 18.0.6, and 18.0.10, the default value for the edpm_network_config_nmstate parameter was set to false. Starting in RHOSO 18.0.14, the default value is true. As a result, when you update your environment from RHOSO 18.0.3, 18.0.6, or 18.0.10 to RHOSO 18.0.14 or later, the NetworkManager.conf file on Compute nodes does not update.

Workaround:

Create instance of openstack during minor update

If you update your Red Hat OpenStack Services on OpenShift environment from any release before 18.0.6, you must create an instance of openstack after you update the openstack-operator to trigger the deployment of all operators. For example:

cat > openstack-init.yaml <<'EOF'
---
apiVersion: operator.openstack.org/v1beta1
kind: OpenStack
metadata: 
   name: openstack 
   namespace: openstack-operators
EOF 

$ oc apply -f ./openstack-init.yaml

Guidance on whether to reboot compute nodes is not refreshed during a minor update

During a minor update to Red Hat OpenStack Services on OpenShift (RHOSO) 18.0.x, there is an option to check the logs to confirm whether your Compute nodes in a specific node set need a reboot. However, the reboot-os service is not run during a minor update. As a result, the logs do not accurately display whether a reboot is required.

Workaround: To ensure that the logs are up to date, complete the following steps:

1. Run a deployment with the reboot-os service. For example:

   apiVersion: dataplane.openstack.org/v1beta1
   kind: OpenStackDataPlaneDeployment
   metadata: 
     name: dataplane-update-reboot-no-force 
     namespace: openstack
   spec: 
     nodeSets: 
       - openstack-edpm 
     servicesOverride: 
       - reboot-os 
     ansibleExtraVars: 
       edpm_reboot_strategy: never

2. Check the logs to confirm which nodes need a reboot:

   $ oc logs jobs/reboot-os-<deployment_name>-<nodeSet_name>

   • Replace <deployment_name> with the name of the deployment that includes your Compute nodes.
   • Replace <nodeSet_name> with the names of the node sets that you need to check.

   The command shows the following output if a reboot is required: Reboot is required but was not started. Edpm_reboot_strategy is set to never or this is already deployed machine. Reboot has to be planned. To start reboot set edpm_reboot_strategy to force.

Control plane temporarily unavailable during minor update

During minor updates, the RHOSO control plane temporarily becomes unavailable. API requests might fail with HTTP error codes, such as error 500. Alternatively, the API requests might succeed but the underlying life cycle operation fails. For example, a virtual machine instance created with the openstack server create command during the minor update never reaches the ACTIVE state. The control plane outage is temporary and automatically recovers after the minor update is finished. The control plane outage does not affect the already running workload.

Workaround:To prevent this disruption, see the How to enable mirrored queues in Red Hat Openstack Services on OpenShift.