-
Bug
-
Resolution: Duplicate
-
None
-
False
-
-
False
-
CLOSED
-
---
-
---
-
-
-
High
-
None
Description of problem:
-----------------------
hco.spec.tlsSecurityProfile was set to 'Old' profile. Then made sure other CNV components' TLS security profile are update accordingly. After removing 'hco.spec.tlsSecurityProfile', SSP pod goes in to CrashLoopBackOff state for a while, the restarts the pod after few seconds
Version-Release number of selected component (if applicable):
--------------------------------------------------------------
CNV v4.12.0
How reproducible:
-----------------
Always
Steps to Reproduce:
-------------------
1. Modify the hco.spec.tlsSecurityProfile to 'Old' policy
- oc patch hco --type=json kubevirt-hyperconverged -n openshift-cnv -p '[{"op": "replace", "path": "/spec/tlsSecurityProfile", "value": {"old": {}, "type": "Old"}}]'
2. Remove the hco.spec.tlsSecurityProfile
- oc patch hco --type=json kubevirt-hyperconverged -n openshift-cnv -p '[
{"op": "replace", "path": "/spec/tlsSecurityProfile", "value": }
]'
3. Check for SSP pods in openshift-cnv namespace
Actual results:
---------------
SSP pods goes in to CrashLoopBackOff state for sometime
<snip>
kubemacpool-cert-manager-754d94cdd7-xsw9r 1/1 Running 0 13h
kubemacpool-mac-controller-manager-588894c6bd-8s9bb 2/2 Running 0 24s
kubevirt-plugin-b4c89cbc6-2r8nx 1/1 Running 0 13h
ssp-operator-5d7cdcdd65-pkr76 0/1 CrashLoopBackOff 32 (28s ago) 13h
</snip>
Expected results:
------------------
SSP operator should not go in to CrashLoopBackOff even for a brief amount of time
- duplicates
-
CNV-23186 [2151248] SSP pods moving to CrashLoopBackOff state for long duration when tlssecurityProfile is changed often
- Closed
- external trackers