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

[release-4.18] Operator is visible twice in management console

XMLWordPrintable

    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, when viewing the list of installed operators and the currently selected project matches an operator's default namespace while copied CSVs are disabled in OLM, an operator appeared twice in the list. With this release, the operator appears once.
      Show
      Previously, when viewing the list of installed operators and the currently selected project matches an operator's default namespace while copied CSVs are disabled in OLM, an operator appeared twice in the list. With this release, the operator appears once.
    • Bug Fix
    • Done

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

          Installed operator page show operator installed twice

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

          OCP version: 4.14, Dynatrace version: 1.4

      How reproducible:

          N/a, not able to reproduce in any version.

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

          Operator show installed twice, one as cluster wide and one in openshift namespace.

      Expected results:

          Operator should be visible as installed in only once

      Additional info:

      - Reinstallation of operator didn't work

- Updating version of operator also gave same result.

- We have tried restart of OLM pods and marketplace pods as well.

- The operator shows installed 2 time where as there is only single sub,csv and ip for operator.

              rhn-engineering-rhamilto Robb Hamilton
              openshift-crt-jira-prow OpenShift Prow Bot
              Yanping Zhang Yanping Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: