Bug 1860791
| Summary: | [OCP v4.6] The ComplianceSuite shows empty status over OLM (UI) after the scan complete | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Prashant Dhamdhere <pdhamdhe> | ||||||||||
| Component: | Compliance Operator | Assignee: | Jakub Hrozek <jhrozek> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Prashant Dhamdhere <pdhamdhe> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 4.6 | CC: | josorior, mrogers, nkinder, ocasalsa, xiyuan | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | 4.6.0 | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2020-10-27 16:17:14 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: |
|
||||||||||||
|
Description
Prashant Dhamdhere
2020-07-27 07:07:26 UTC
I started looking into this, so far I was able to reproduce the behaviour and I asked for pointers on #forum-ui. btw the empty columns are not displayed only for Scans, but also for CheckResults etc. It looks like the console is not really honoring the `additionalPrinterColumns` the CRDs specify. I'll update the bug again once I have some reply about how is the UI rendered. So, we could fix the complianceSuite status by switching the field name from .status.aggregatedPhase to .status.Phase. But the other CRs would still show nothing. Unsure if it's worth it. Long-term I guess implementing a console plugin is a more systematic way. Matt, Ozz, what do you think? https://github.com/openshift/compliance-operator/pull/405 updated to be non-WIP. Note that the patch only fixes Suites, not e.g. Remediations or Checks Merged as https://github.com/openshift/compliance-operator/commit/59cde7c7aa131c5b3938766f4dbc5c736a1d0e0c This looks good now, The ComplianceSuite shows proper status over OLM (UI) during & after the scan complete. Attaching some screenshots (Csuite-launching-2020-09-08 11-57-29.png, Csuite-aggregating-2020-09-08 12-01-14.png, csuite-done- 2020-09-08 12-02-21.png) Verified on: 4.6.0-0.nightly-2020-09-07-224533 $ oc get compliancesuite NAME PHASE RESULT example-compliancesuite DONE NON-COMPLIANT $ oc get compliancescan NAME PHASE RESULT platform-scan DONE NON-COMPLIANT workers-scan DONE NON-COMPLIANT Created attachment 1714056 [details]
Csuite-launching
Created attachment 1714059 [details]
Csuite-aggregating
Created attachment 1714061 [details]
Csuite-done
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 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 |