Bug 1925461 - Compliance operator is not displayed when disconnected mode is selected in the OpenShift Web-Console.
Summary: Compliance operator is not displayed when disconnected mode is selected in th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Compliance Operator
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.7.0
Assignee: Jakub Hrozek
QA Contact: Prashant Dhamdhere
URL:
Whiteboard:
Depends On:
Blocks: 1920999
TreeView+ depends on / blocked
 
Reported: 2021-02-05 09:34 UTC by xiyuan
Modified: 2021-03-08 10:36 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1920999
Environment:
Last Closed: 2021-03-08 10:36:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Juan Antonio Osorio 2021-02-05 09:39:46 UTC 
Fixed in https://github.com/openshift/compliance-operator/pull/558
Comment 2 xiyuan 2021-02-05 13:26:19 UTC 
Verification pass with payload 4.7.0-0.nightly-2021-02-04-183139 and 4.7 compliance-operator.v0.1.25. 
With upi GCP disconnected cluster, use OpenShift Web UI, Select Operator Hub -> Infrastructure Feature -> Disconnected,
it will show the Compliance operator when the disconnected filter is applied.
Below is the version used for verification.
$ oc get ip
NAME            CSV                           APPROVAL    APPROVED
install-2zx87   compliance-operator.v0.1.25   Automatic   true
$ oc get csv
NAME                          DISPLAY               VERSION   REPLACES   PHASE
compliance-operator.v0.1.25   Compliance Operator   0.1.25               Succeeded
Comment 3 xiyuan 2021-02-05 13:27:06 UTC 
Per comment https://bugzilla.redhat.com/show_bug.cgi?id=1925461#c2, move it to Verified.
Comment 4 Jakub Hrozek 2021-03-08 10:36:52 UTC 
This bug has been fixed in 4.7.0 (see comment #2) but somehow slipped out of the 4.7.0 errata. Closing as CURRENTRELEASE, then.
btw the bug was also closed in 4.6.z as https://bugzilla.redhat.com/show_bug.cgi?id=1920999
Note You need to log in before you can comment on or make changes to this bug.