Bug 1925190

Summary: Unable to remove the value for HTTP(S) proxy except hosts in settings page
Product: Red Hat Satellite Reporter: Anand Agrawal <aagrawal>
Component: SettingsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Devendra Singh <desingh>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.9.0CC: apatel, mhulan
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1925193 (view as bug list) Environment:
Last Closed: 2021-02-08 14:18:11 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:
Bug Depends On:    
Bug Blocks: 1925193    

Description Anand Agrawal 2021-02-04 14:55:40 UTC 
Description of problem:
Once we set the value for HTTP(S) proxy except hosts in settings, we can not empty this value. 

Following error is seen:
Oh no! Something went wrong while submitting the form, the server returned the following error: Error: Request failed with status code 422

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

How reproducible:
Always

Steps to Reproduce:
1. Goto Administer -> Settings -> Add any value for HTTP(S) proxy except hosts	
2. Click submit.
3. Refresh page to refresh the value (This is also a bug), In earlier version, it reflected without page refresh.
4. Now remove the value from HTTP(S) proxy except hosts, and submit, this will throw above error

Actual results:


Oh no! Something went wrong while submitting the form, the server returned the following error: Error: Request failed with status code 422

Expected results:

It should allow to reset the value
Additional info:
Comment 1 Devendra Singh 2021-02-04 15:48:25 UTC 
It looks duplicate of BZ#1914256
Comment 2 Brad Buckingham 2021-02-08 14:18:11 UTC 
As mentioned in comment 1, this appears to be a duplicate; therefore, closing.  Please do re-open if there are concerns.  Thanks!

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