Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-36764

Block all z rollbacks again

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.16.z
    • 4.16, 4.17
    • Cluster Version Operator
    • None
    • Moderate
    • None
    • OTA 256
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      The undocumented, dev-preview, environment-variable gated 'oc adm upgrade rollback' command has been removed, along with the associated gap in the cluster-version operator's rollback guard. Now all rollbacks are blocked again, unless a cluster administrator forces through the guard. Rollbacks re-expose the cluster to fixed bugs and move many aspects of the cluster that are unrelated to the concerning issue in minimally tested ways. We strongly encourage administrators to contact Red Hat support, apply workaround mitigations, and roll forward into fixes.
      Show
      The undocumented, dev-preview, environment-variable gated 'oc adm upgrade rollback' command has been removed, along with the associated gap in the cluster-version operator's rollback guard. Now all rollbacks are blocked again, unless a cluster administrator forces through the guard. Rollbacks re-expose the cluster to fixed bugs and move many aspects of the cluster that are unrelated to the concerning issue in minimally tested ways. We strongly encourage administrators to contact Red Hat support, apply workaround mitigations, and roll forward into fixes.
    • Removed Functionality
    • In Progress

      This is a clone of issue OCPBUGS-35994. The following is the description of the original issue:
      —

      Description of problem

      To reduce QE load, we've decided to block up the hole drilled in OCPBUGS-24535. We might not want a pure revert, if some of the changes are helpful (e.g. more helpful error messages).

      We also want to drop the oc adm upgrade rollback subcommand which was the client-side tooling associated with the OCPBUGS-24535 hole.

      Version-Release number of selected component

      Both 4.16 and 4.17 currently have the rollback subcommand and associated CVO-side hole.

      How reproducible

      Every time.

      Steps to Reproduce

      Try to perform the rollbacks that OCPBUGS-24535 allowed.

      Actual results

      They work, as verified in OCPBUGS-24535.

      Expected results

      They stop working, with reasonable ClusterVersion conditions explaining that even those rollback requests will not be accepted.

              Unassigned Unassigned
              openshift-crt-jira-prow OpenShift Prow Bot
              Evgeni Vakhonin Evgeni Vakhonin
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: