-
Bug
-
Resolution: Won't Do
-
Critical
-
rhos-18.0 FR 2 (Mar 2025)
-
None
-
2
-
False
-
-
False
-
?
-
None
-
-
Release Note Not Required
-
-
-
Important
In 2.1. Updating OVN services on the control plan we switch from having the openstack operator updated (install plan accepted) to udating the openstackversion.
But, now after the update of the openstack-operator, we don't have the version available right away, we need to create an instance of openstack.
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
Then we get access to the new version using `oc get openstackversion` and we can proceed with the rest of the update.
Note that that step has been added to the release note for deployment. I think it's important to notify the user where it fits during an update also.