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

failure to upgrade OLM packageserver does not block OCP upgrade

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • 4.9.z
    • OLM
    • Important
    • Yamask 233, Zuko 234
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

       

      When a OCP 4.8 cluster is upgrade to the latest 4.9.z ( 4.9.47 at the time this report was written), the packageserver stays stuck in v0.17.0, even though the v0.18.3 packgeserver is supposed to roll out. Instead the packgeserver stays stuck in v0.17.0. However, the OLM clusteroperator does not report any failure, inaccurately stating that all of OLM's components were upgraded successfully, and therefore the upgrade was successful.

      Version-Release number of selected component (if applicable):

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Launch 4.8
2. Upgrade to 4.9.47

      Actual results:

      Upgrade happens successfully, despite https://issues.redhat.com/browse/OCPBUGS-858 preventing the packageserver from moving to v0.17.0 to v0.18.3

      Expected results:

      Upgrade is blocked if packageserver CSV (a core component of OLM) is not upgraded to the expected version.

      Additional info:

       

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-858 package-server-manager does not migrate packageserver CSV from v0.17.0 to v0.18.3 on OCP 4.8 -> 4.9 upgrade

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-776 The lacking securityContext.seccompProfile.type of OLM's packageserver deployment is blocking OCP upgrade to 4.12

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rh-ee-dfranz Daniel Franz
              anik120 Anik Bhattacharjee
              Jian Zhang Jian Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: