Hi Prashant, this appears to be fixed with recent versions as well. I suspect the root cause was the same as with https://bugzilla.redhat.com/show_bug.cgi?id=1795193. Can you please check if you see the same? If yes, maybe we can close the bug.
Hi Jakub, Yes, this issue has been fixed and now, the ComplianceScan pods status is showing the same over CLI and GUI. Verified on : 4.5.0-0.nightly-2020-06-23-020504
Also verified on : 4.6.0-0.nightly-2020-07-07-233934 The worker-scan pods status shows "Succeeded" now, also the pods status looks good over GUI $ oc get pods |tail -2 workers-scan-ip-10-0-62-228.us-east-2.compute.internal-pod 0/2 Completed 0 11m workers-scan-ip-10-0-75-245.us-east-2.compute.internal-pod 0/2 Completed 0 11m $ oc describe pod workers-scan-ip-10-0-62-228.us-east-2.compute.internal-pod |grep Status: Status: Succeeded
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