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

Cluster Upgrade olm.maxOpenShiftVersion should clarify MINOR, MAJOR

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • 4.13, 4.12, 4.14
    • OLM
    • Quality / Stability / Reliability
    • None
    • None
    • None
    • Low
    • None
    • Unspecified
    • None
    • None
    • Rejected
    • None
    • None
    • If docs needed, set a value
    • None
    • None
    • None
    • None
    • None

      Description of problem: When on cluster upgrade page of OpenShift web console olm.maxOpenShiftVersion related warnings should include more universal language for people who don't understand semver.

      ie.

      • 4.8 cluster cannot be upgraded to 4.9 due to olm.maxOpenShiftVersion
      • 4.99 cluster cannot be upgraded to 5.0 due to olm.maxOpenShiftVersion

      instead of "operator something something ... has olm.maxOpenShiftVersion which prevents MINOR ocp upgrade"

      Version-Release number of selected component (if applicable): 4.12, 4.13, ...

      Motivation: have received customer calls where they want hand holding and blessing because current warning are not assuring to them when upgrading patches within the same MINOR version.

              agreene1991 Alexander Greene (Inactive)
              tkaovila@redhat.com Tiger Kaovilai
              Daniel Messer
              None
              Xia Zhao Xia Zhao
              None
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: