Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1925193 - Unable to add the value for HTTP(S) proxy in settings page
Summary: Unable to add the value for HTTP(S) proxy in settings page
Keywords:
Status: CLOSED DUPLICATE of bug 1911228
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Settings
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On: 1914256 1925190
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-04 15:01 UTC by Anand Agrawal
Modified: 2021-05-06 07:54 UTC (History)
7 users (show)

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.
Clone Of: 1925190
Environment:
Last Closed: 2021-05-06 07:49:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.