Bug 2109300 - unable to unset the "CDN SSL version" settings from UI of Satellite
Summary: unable to unset the "CDN SSL version" settings from UI of Satellite
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Settings
Version: 6.11.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-20 22:03 UTC by Ganesh Payelkar
Modified: 2023-07-21 21:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.