Bug 1925193

Summary: Unable to add the value for HTTP(S) proxy 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: high Docs Contact:
Priority: high    
Version: 6.9.0CC: apatel, desingh, jyejare, mhulan, satellite6-bugs, smallamp, tbrisker
Target Milestone: UnspecifiedKeywords: Regression, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Cause: 1. Goto Administer -> Settings 2. Add a url for "HTTP(S) proxy" without including "http://". For example, "myproxy.com" Consequence: An error such as the following is displayed: "Oh no! Something went wrong while submitting the form" Workaround (if any): For the "HTTP(S) proxy" setting, include the "http://" in the value. For example, "http://myproxy.com" Result: With the workaround, the proxy setting should be saved without error.
Story Points: ---
Clone Of: 1925190 Environment:
Last Closed: 2021-05-06 07:49:42 UTC Type: ---
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: 1914256, 1925190    
Bug Blocks:    

Description Anand Agrawal 2021-02-04 15:01:17 UTC
Description of problem:

Unable to add value for HTTP(S) proxy

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 
2. Click submit.
3. 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 adding the value

Additional info:

Comment 1 Devendra Singh 2021-02-04 15:47:42 UTC
It looks duplicate of BZ#1918167

Comment 2 Brad Buckingham 2021-03-08 20:47:56 UTC
Hi Anand,

Can you take a quick peak at the bug mentioned in comment 1 to confirm if this is the same behavior that you saw?

The description is slightly different; however, it does look like it may be the same issue.

Thanks!

Comment 3 Anand Agrawal 2021-03-09 02:24:30 UTC
Hello Brad,

Thank you for highlighting this. I do not think the bug mentioned in comment 1 has same behaviour as this bug.

In my latest snap of beta, it seems the other bug is fixed but not this one.

In bug #1918167, it talks about  content tab, but this bug is for `HTTP(S) proxy` in General tab.

Further testing, I can see if we add the `HTTP(S) proxy` in the form of http://example.com, it works as expected or if we clear the `HTTP(S) proxy` completely it works.

But if we add the proxy anything else like 'example.com' without 'http://' it would throw the error as mentioned.

Let me know if I can help you with any further detail.

Regards,
Anand

Comment 4 Sudhir Mallamprabhakara 2021-03-16 18:54:44 UTC
Anand - Is this a regression or an existing bug that we have never reported?

Comment 5 Anand Agrawal 2021-03-18 01:06:50 UTC
(In reply to Sudhir Mallamprabhakara from comment #4)
> Anand - Is this a regression or an existing bug that we have never reported?

Sudhir,

This is a regression. 

In Sat 6.8, It shows a nice, clean & formatted (css) for the error as "Not a valid URL for a HTTP Proxy"

In Sat6.9, It shows unclear message as "Oh no! Something went wrong while submitting the form, the server returned the following error: Error: Request failed with status code 422"

Regards,
Anand

Comment 6 Sudhir Mallamprabhakara 2021-03-23 02:10:22 UTC
Adding regression keyword based on Comment 5

Comment 7 Brad Buckingham 2021-03-23 13:08:21 UTC
Based upon discussion in Satellite standup, our recommendation is to propose this for a Satellite 6.9 zstream, once a fix is available.  The issue as described shouldn't block the current release as there is a straight forward workaround mentioned in comment 5.

Adding flagging to request a known issue to be added to the release notes.

Comment 9 Tomer Brisker 2021-05-06 07:49:42 UTC
retested on Satellite 6.9.1, this is fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1911228. Closing as duplicate as this is the same root cause (error responses were not displayed correctly).
Entering an invalid value for http proxy shows correct error message:
"Oh no! Something went wrong while submitting the form, the server returned the following error: Not a valid URL for a HTTP Proxy"

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