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

Default CatalogSource aren't always reverted to default settings

    XMLWordPrintable

Details

    • Low
    • Voltron 230, Windu 231
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Operator Lifecycle Manager (OLM) manages a set of `CatalogSource` objects from which Operators can be searched for and installed from. These catalog sources are the default sources for this action and are managed by Red Hat. However, it was possible to change these default catalog sources in a way that the OLM system would not notice. Modifying a default catalog source in a way that rendered it inoperable could cause cascading issues through OLM that could prevent a user from installing new or upgrading existing Operators on their cluster. This bug fix updates the `catalog-operator` runtime, which manages the default catalog sources, to be made aware of other changes to the `CatalogSource` spec. As a result, when a change is made to a default catalog source, OLM detects the change and resets it back to default. (link:https://issues.redhat.com/browse/OCPBUGS-5466[*OCPBUGS-5466*])
      Show
      * Operator Lifecycle Manager (OLM) manages a set of `CatalogSource` objects from which Operators can be searched for and installed from. These catalog sources are the default sources for this action and are managed by Red Hat. However, it was possible to change these default catalog sources in a way that the OLM system would not notice. Modifying a default catalog source in a way that rendered it inoperable could cause cascading issues through OLM that could prevent a user from installing new or upgrading existing Operators on their cluster. This bug fix updates the `catalog-operator` runtime, which manages the default catalog sources, to be made aware of other changes to the `CatalogSource` spec. As a result, when a change is made to a default catalog source, OLM detects the change and resets it back to default. (link: https://issues.redhat.com/browse/OCPBUGS-5466 [* OCPBUGS-5466 *])
    • Bug Fix
    • Done

    Description

      Description of problem:

      It is possible to change some of the fields in default catalogSource specs and the Marketplace Operator will not revert the changes

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

      4.13.0 and back

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create a 4.13.0 OpenShift cluster
2. Set the redhat-operator catalogSource.spec.grpcPodConfig.SecurityContextConfig field to `legacy`.

      Actual results:

      The field remains set to `legacy` mode.

      Expected results:

      The field is reverted to `restricted` mode.

      Additional info:
      This code needs to be updated to account for new fields in the catalogSource spec.

       

       

       

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-7108 Default CatalogSource aren't always reverted to default settings

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-7108 Default CatalogSource aren't always reverted to default settings

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub operator-framework/operator-marketplace#504: OCPBUGS-5466: Default CatalogSource aren't always reverted to default settings

          Activity

            People

              agreene1991 Alexander Greene
              agreene1991 Alexander Greene
              Jian Zhang Jian Zhang
              Alex Dellapenta Alex Dellapenta
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: