Bug 2109300

Summary: unable to unset the "CDN SSL version" settings from UI of Satellite
Product: Red Hat Satellite Reporter: Ganesh Payelkar <gpayelka>
Component: SettingsAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: apatel, mhulan, nalfassi
Target Milestone: UnspecifiedKeywords: Triaged, WorkAround
Target Release: Unused   
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: 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 Ganesh Payelkar 2022-07-20 22:03:37 UTC 
Description of problem:

unable to unset the "CDN SSL version" settings from the UI of Satellite

Version-Release number of selected component (if applicable):
satellite-6.11

How reproducible:


Steps to Reproduce:
1. Visit to WebUI --> admin --> settings --> content --> CDN SSL version
2. Change the value from the drop-down  SSLv23 and TLSv1
3. Now if you do not need any of these values, you can not change it to Default "Empty"

Actual results:

We can not unset the value to set the Empty value in the BOX 

Expected results:

Need an option to unset the value 


Additional info:

# hammer settings info --name cdn_ssl_version
Id:            cdn_ssl_version
Name:          cdn_ssl_version
Description:   SSL version used to communicate with the CDN
Category:      Content
Settings type: 
Value:         TLSv1


To unset the value : 

# hammer settings set --name cdn_ssl_version --value=''
Comment 1 Brad Buckingham 2023-07-21 21:06:39 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.