Bug 2141419

Summary: Unable to set TLS Security profile for CNAO using HCO jsonpatch annotations
Product: Container Native Virtualization (CNV) Reporter: SATHEESARAN <sasundar>
Component: InstallationAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED DUPLICATE QA Contact: SATHEESARAN <sasundar>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.12.0CC: cnv-qe-bugs, stirabos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-10 17:34:26 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:

Description SATHEESARAN 2022-11-09 19:09:07 UTC
Description of problem:
------------------------
Attempt to set the TLS security profile for CNAO fails

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
kubevirt-hyperconverged-operator.4.12.0-684

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Apply HCO jsonpatch annotation to update TLS security profile for CNAO

# oc annotate --overwrite -n openshift-cnv hco kubevirt-hyperconverged networkaddonsconfigs.kubevirt.io/jsonpatch='[{"op": "replace", "path": "/spec/tlsSecurityProfile", "value": {"old":{}, "type": "Old"}}]'

2. Get the TLS security profile set on CNAO
# oc get networkaddonsconfig cluster -n openshift-cnv -ojsonpath={.spec.tlsSecurityProfile}

Actual results:
---------------
CNAO has got incorrect definition for 'tlsSecurityProfile' as:
[cnv-qe-jenkins@ ~]$ oc get networkaddonsconfig cluster -n openshift-cnv -ojsonpath={.spec.tlsSecurityProfile}
{"intermediate":{},"old":{},"type":"Old"}[

Expected results:
-----------------
CNAO should contain the right definition ( not the mix of 2 TLS profiles ) for TLS security profile.
{"old":{}, "type": "Old"}

Additional info:
----------------
Also tested with 'Custom' TLS profile and still there is a mix of 'intermediate' TLS profile with the 'Custom' profile

Comment 1 Simone Tiraboschi 2022-11-10 17:34:26 UTC

*** This bug has been marked as a duplicate of bug 2141399 ***