Bug 1840984
| Summary: | [OCP 45] Need to re-frame compliance operator description which displays over the console | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Prashant Dhamdhere <pdhamdhe> | ||||
| Component: | Compliance Operator | Assignee: | Jakub Hrozek <jhrozek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Prashant Dhamdhere <pdhamdhe> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.5 | CC: | josorior, mrogers, xiyuan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.6.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | v0.1.10 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-10-27 16:01:53 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 1692940 [details]
Compliance Operator description
This should be fixed with the 0.1.10 release that went out yesterday, could you please check if the text now looks good? The compliance operator description looks good now over OLM console but
we still need to re-frame or correct it in clusterserviceversion.yaml file.
$ grep -A3 "description: |" compliance-operator/deploy/olm-catalog/compliance-operator/0.1.10/compliance-operator.v0.1.10.clusterserviceversion.yaml
description: |
An operator which runs OpenSCAP and allows you to check your cluster for
security vulnerabilities and to keep your it compliant with the
security benchmark you need. ^^^^^^^^^^^^^^^^^^^^^^
--
description: |
An operator which runs OpenSCAP and allows you to check your cluster for
security vulnerabilities and to keep it compliant with the
security benchmark you need.
(In reply to Prashant Dhamdhere from comment #5) > The compliance operator description looks good now over OLM console but > we still need to re-frame or correct it in clusterserviceversion.yaml file. > > $ grep -A3 "description: |" > compliance-operator/deploy/olm-catalog/compliance-operator/0.1.10/compliance- > operator.v0.1.10.clusterserviceversion.yaml > description: | > An operator which runs OpenSCAP and allows you to check your cluster > for > security vulnerabilities and to keep your it compliant with the > security benchmark you need. ^^^^^^^^^^^^^^^^^^^^^^ > -- > description: | > An operator which runs OpenSCAP and allows you to check your cluster for > security vulnerabilities and to keep it compliant with the > security benchmark you need. Thank you, I submitted another PR as https://github.com/openshift/compliance-operator/pull/383 but we won't be able to close the bug until the next release is cut. Fixed upstream: https://github.com/openshift/compliance-operator/commit/e6554a81ef08e3014f41c336a7358f0a714fec98 The compliance operator description looks good now at both the places.
Verified with compliance operator v0.1.13
$ grep "name:\|version" compliance-operator/deploy/olm-catalog/compliance-operator/0.1.13/compliance-operator.v0.1.13.clusterserviceversion.yaml |head -1
name: compliance-operator.v0.1.13
$ grep -A3 "description: |" compliance-operator/deploy/olm-catalog/compliance-operator/0.1.13/compliance-operator.v0.1.13.clusterserviceversion.yaml
description: |
An operator which runs OpenSCAP and allows you to check your cluster for
security vulnerabilities and to keep it compliant with the
security benchmark you need.
--
description: |
An operator which runs OpenSCAP and allows you to check your cluster for
security vulnerabilities and to keep it compliant with the
security benchmark you need.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196 |
Description of problem: The following compliance operator description displays over the console after deploying it through OLM. Need to re-frame the description. $ grep -A3 "description: |" deploy/olm-catalog/compliance-operator/0.1.9/compliance-operator.v0.1.9.clusterserviceversion.yaml description: | An operator which runs OpenSCAP and allows you to check your cluster for security vulnerabilities and to keep your it compliant with the security benchmark you need. ^^^^^^^^^^^^^^^^^^^^^^^^^ Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-05-27-010813 How reproducible: Always Steps to Reproduce: 1.clone git repo $ git clone https://github.com/openshift/compliance-operator.git 2.Login through kubeadmin user $ oc login -u kubeadmin -p <pw> 3.Create project with 'openshift-compliance' name $ oc create namespace openshift-compliance 4.Deploy compliance-operator from OLM $ oc create -f compliance-operator/deploy/olm-catalog/operator-source.yaml 5.Login through the console using kubeadmin user 6.Click on Operators --> OperatorHub and search for Compliance Operator 7.Click on Compliance Operator to install and you can see Compliance Operator description infront of Operator Version Actual results: The compliance operator description has "your" word and because of that, the description does not look appropriate Expected results: The compliance operator description should look appropriate Additional info: