Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-25444

Missing Verification Step for Control Plane Update in RHOSO Minor Update Docs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhos-18.0.z
    • rhos-18.0.10 FR 3
    • documentation
    • Bug Tracking
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • rhos-ops-day1day2-upgrades
    • None
    • Hide

      Based on RHOSPPRIO-827 feedback

      The minor update documentation lacks a clear verification step to confirm when the automatic update of the "remaining control plane services" is complete. Users are currently required to guess or move to the data plane update (Step 2.4) without a definitive signal that the control plane is ready.

      2.2. Updating OVN services on the control plane
      2.3. Updating OVN services on the data plane
      2.4. Updating the remaining services on the data plane

      The text in 2.4 states:

      "When the OVN service is updated on the control plane and data plane, and the OpenStack Operator has completed the automatic update of the remaining control plane packages... you must update the remaining services on the data plane."

      The Issue: There is no explicit instruction or command telling the operator how to verify that the "automatic update of the remaining control plane packages" has actually finished. This has led to customer confusion and queries regarding the expected state of the environment.

      Suggested Improvement

      Insert a formal verification step (either as a new sub-section or a note at the end of 2.2) that provides a command to wait for the control plane update condition.

      Proposed Command: Operators should be instructed to run a command similar to the one used in internal documentation to ensure the environment is ready for the data plane update:

      oc wait $OPENSTACK_VERSION_CR --for=condition=MinorUpdateControlplane --timeout=$TIMEOUT
      
      Show
      Based on RHOSPPRIO-827 feedback The minor update documentation lacks a clear verification step to confirm when the automatic update of the "remaining control plane services" is complete. Users are currently required to guess or move to the data plane update (Step 2.4) without a definitive signal that the control plane is ready. 2.2. Updating OVN services on the control plane 2.3. Updating OVN services on the data plane 2.4. Updating the remaining services on the data plane The text in 2.4 states: "When the OVN service is updated on the control plane and data plane, and the OpenStack Operator has completed the automatic update of the remaining control plane packages... you must update the remaining services on the data plane." The Issue: There is no explicit instruction or command telling the operator how to verify that the "automatic update of the remaining control plane packages" has actually finished. This has led to customer confusion and queries regarding the expected state of the environment. Suggested Improvement Insert a formal verification step (either as a new sub-section or a note at the end of 2.2) that provides a command to wait for the control plane update condition. Proposed Command: Operators should be instructed to run a command similar to the one used in internal documentation to ensure the environment is ready for the data plane update: oc wait $OPENSTACK_VERSION_CR -- for =condition=MinorUpdateControlplane --timeout= $TIMEOUT
    • Moderate

      Missing Verification Step for Control Plane Update in RHOSO Minor Update Docs

              kgilliga@redhat.com Katie Gilligan
              rhn-engineering-sgolovat Sergii Golovatiuk
              rhos-dfg-upgrades
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: