-
Bug
-
Resolution: Done
-
Undefined
-
ACM 2.12.0
-
0
-
False
-
None
-
False
-
-
-
GRC Sprint 2024-18, GRC Sprint 2024-19
-
Moderate
-
None
Description of problem:
In an upgrade environment described in https://issues.redhat.com/browse/ACM-14100 , certificate policies created prior to upgrade to 2.11.3 have reported a different status than the policies created after upgrade. See attached image.
Check with mprahl , this could be a racing condition and needs more investigation.
Version-Release number of selected component (if applicable):
ACM 2.11.3 - Y-Upgrade on VMWARE OCP 4.14 --> 2.8.z --> 2.9.z --> 2.10.z --> 2.11.3
How reproducible:
Always
Steps to Reproduce:
- Created a cert policy on clusters like ocp 311 and openshift clusters before upgrade
- Perform upgrade to 2.11.3
- Created another cert policy on the same clusters
Actual results:
The results of the first policy showed different violation status of the clusters than the status by the second policy
Expected results:
Both policies show the same violation results for the clusters
Additional info:
- clones
-
ACM-14436 Certificate policies result status were not updated after ACM hub has been upgraded to 2.11.3
- Testing