This is a clone of issue OCPBUGS-52838. The following is the description of the original issue:
—
Description of problem:
When the IO pulls SCA cert with an unexpected response(like "{}"), the msg description in the SCAAvailable condition isn't accurate and it's easy to misundertand.
Version-Release number of selected component (if applicable):
How reproducible:
Run the test case named test_pulling_sca_certs_unexpected_response, this case will create a mocking pod that returns a response with 500 then updating this pod as SCA endpoint.
Steps to Reproduce:
1. Run the test case named test_pulling_sca_certs_unexpected_response
2. Check the msg description in the SCAAvailable condition.
Actual results:
1. The msg description is node architecture not found
Expected results:
1. The msg description should be something like 'certificates for node architecture not found, default secret is not created nor updated'
Additional info:
- clones
-
OCPBUGS-52838 The msg description in the SCAAvailble condition isn't accurate enough when failing to parse the response
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to
- mentioned on
