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

package-server-manager does not stomp on changes made to packgeserver CSV

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.12
    • OLM
    • None
    • None
    • [OLM-224] FBC/PSA - Pikachu
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      Before the {product-title} {product-version} release, the `package-server-manager` controller would not revert any changes made to a `package-server` cluster service version (CSV), because of an issue with the `on-cluster` function. These persistent changes might impact how an Operator starts in a cluster.

      For {product-title} {product-version}, the `package-server-manager` controller always rebuilds a `package-server` CSV to its original state, so that no modifications to the CSV persist after a cluster upgrade operation. The `on-cluster` function no longer controls the state of a`package-server` CSV.

      (link:https://issues.redhat.com/browse/OCPBUGS-867[*OCPBUGS-867*])
      Show
      Before the {product-title} {product-version} release, the `package-server-manager` controller would not revert any changes made to a `package-server` cluster service version (CSV), because of an issue with the `on-cluster` function. These persistent changes might impact how an Operator starts in a cluster. For {product-title} {product-version}, the `package-server-manager` controller always rebuilds a `package-server` CSV to its original state, so that no modifications to the CSV persist after a cluster upgrade operation. The `on-cluster` function no longer controls the state of a`package-server` CSV. (link: https://issues.redhat.com/browse/OCPBUGS-867 [* OCPBUGS-867 *])
    • Bug Fix
    • Done

      Description of problem:

       

      Changes to the packageserver, being managed by the package-server-manager, are not reset.

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

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. install OCP 4.12
2. edit the packageserver CSV to delete the deployment.spec.securityContext.runAsRoot field

      Actual results:

      the field stays deleted in the CSV

      Expected results:

      CSV is reset back to contain the field again.

      Additional info:

      Affects version 4.12->4.9, when package-server-manager was introduced. Fix needs to be backported.

              agreene1991 Alexander Greene (Inactive)
              anik120 Anik Bhattacharjee
              Jian Zhang Jian Zhang
              Darragh Fitzmaurice Darragh Fitzmaurice
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: