-
Bug
-
Resolution: Done
-
Normal
-
rhos-17.1.z
-
None
-
1
-
False
-
-
False
-
?
-
rhos-ops-day1day2-upgrades
-
None
-
-
-
-
-
RHOS Upgrades 2025 Sprint 17
-
1
-
Moderate
The following document says "Optional".
3.3. Optional: Updating the ovn-controller container on all overcloud servers If you deployed your overcloud with the Modular Layer 2 Open Virtual Network mechanism driver (ML2/OVN), update the ovn-controller container to the latest RHOSP 17.1 version. The update occurs on every overcloud server that runs the ovn-controller container. - The following procedure updates the ovn-controller containers on servers that are assigned the Compute role before it updates the ovn-northd service on servers that are assigned the Controller role. - For distributed compute node (edge) architectures, you must complete this procedure for each stack with Compute, DistributedCompute, or DistributedComputeHCI nodes before proceeding with section Updating all Controller nodes. If you accidentally updated the ovn-northd service before following this procedure, you might not be able to connect to your virtual machines or create new virtual machines or virtual networks. The following procedure restores connectivity.
Indeed, we should skip this part when the cluster is using ML2/OVS.
But when the cluster is using ML2/OVN, this step is mandatory and we must not skip it.
If we skip this, we will have network reachability issues on instances.
I've seen several customers who skipped this step and experienced the network issue.
They were mis-leaded by the "Optional" in the document.
I think we should remove "Optional" from it.
My suggestion is
- (*1) Remove "Optional:"
- (*2) Add a note describing that this step can be skipped only when we use ML2/OVS
- (*3) Append a bullet point to the third item, because this is obviously different from the second bullet point.
(*1)
|
V
3.3. Updating the ovn-controller container on all overcloud servers
(*2)
|
V
Note: Skip this step if the OpenStack cluster uses ML2/OVS. This step is required if the OpenStack cluster uses ML2/OVN.
If you deployed your overcloud with the Modular Layer 2 Open Virtual Network mechanism driver (ML2/OVN), update the ovn-controller container to the latest RHOSP 17.1 version. The update occurs on every overcloud server that runs the ovn-controller container.
- The following procedure updates the ovn-controller containers on servers that are assigned the Compute role before it updates the ovn-northd service on servers that are assigned the Controller role.
- For distributed compute node (edge) architectures, you must complete this procedure for each stack with Compute, DistributedCompute, or DistributedComputeHCI nodes before proceeding with section Updating all Controller nodes.
(*3)
|
V
- If you accidentally updated the ovn-northd service before following this procedure, you might not be able to connect to your virtual machines or create new virtual machines or virtual networks. The following procedure restores connectivity.
