Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
unable to set "Default HTTP Proxy" field to "no global default".
Version-Release number of selected component (if applicable):
- Satellite 6.9.0 snap 9
How reproducible:
- Always
Steps to Reproduce:
1. Create a Http Proxy (Go to Infrastructure > Http Proxies)
2. Go to Administer > Settings > Content tab
3. Set "Default HTTP Proxy"
4. Now try to set "Default HTTP Proxy" to "no global default".
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:
- User is able to set "Default HTTP Proxy" to "no global default".
Additional info:
2021-01-20T03:42:34 [E|app|9a9bad14] Unprocessable entity Setting::Content (id: 198):
9a9bad14 | There is no such HTTP Proxy
9a9bad14 |
2021-01-20T03:42:34 [I|app|9a9bad14] Rendering api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout
2021-01-20T03:42:34 [I|app|9a9bad14] Rendered api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout (Duration: 4.8ms | Allocations: 6575)
2021-01-20T03:42:34 [D|app|9a9bad14] Body: {
9a9bad14 | "error": {"id":198,"errors":{"base":["There is no such HTTP Proxy"]},"full_messages":["There is no such HTTP Proxy"]}
9a9bad14 | }
9a9bad14 |
2021-01-20T03:42:34 [I|app|9a9bad14] Completed 422 Unprocessable Entity in 26ms (Views: 8.4ms | ActiveRecord: 3.1ms | Allocations: 18645)
Workaround:
- Use hammer CLI to unset content_default_http_proxy
hammer> settings set --name content_default_http_proxy --value ""
This seems to be fixed already in the upstream. For some reason, the form submission sends the text "no global default" instead of "". The same works for host_owner setting though, which seems to be implemented the same way. I was unable to find the fix in the upstream repos.
FailedQA
Tested on:
- Satellite 6.9.0 snap 16
Test steps:
1. Create a Http Proxy (Go to Infrastructure > Http Proxies)
2. Go to Administer > Settings > Content tab
3. Set "Default HTTP Proxy"
4. Now try to set "Default HTTP Proxy" to "no global default".
Actual results:
Oh no! Something went wrong while submitting the form, the server returned the following error: There is no such HTTP Proxy
Verified:
Verified with:
- Satellite 6.9.0 snap 17
Test steps:
1. Create a Http Proxy (Go to Infrastructure > Http Proxies)
2. Go to Administer > Settings > Content tab
3. Set "Default HTTP Proxy"
4. Now set "Default HTTP Proxy" to "no global default".
Observations:
- Successfully set "Default HTTP Proxy" field to "no global default".
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:1313
Description of problem: unable to set "Default HTTP Proxy" field to "no global default". Version-Release number of selected component (if applicable): - Satellite 6.9.0 snap 9 How reproducible: - Always Steps to Reproduce: 1. Create a Http Proxy (Go to Infrastructure > Http Proxies) 2. Go to Administer > Settings > Content tab 3. Set "Default HTTP Proxy" 4. Now try to set "Default HTTP Proxy" to "no global default". 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: - User is able to set "Default HTTP Proxy" to "no global default". Additional info: 2021-01-20T03:42:34 [E|app|9a9bad14] Unprocessable entity Setting::Content (id: 198): 9a9bad14 | There is no such HTTP Proxy 9a9bad14 | 2021-01-20T03:42:34 [I|app|9a9bad14] Rendering api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout 2021-01-20T03:42:34 [I|app|9a9bad14] Rendered api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout (Duration: 4.8ms | Allocations: 6575) 2021-01-20T03:42:34 [D|app|9a9bad14] Body: { 9a9bad14 | "error": {"id":198,"errors":{"base":["There is no such HTTP Proxy"]},"full_messages":["There is no such HTTP Proxy"]} 9a9bad14 | } 9a9bad14 | 2021-01-20T03:42:34 [I|app|9a9bad14] Completed 422 Unprocessable Entity in 26ms (Views: 8.4ms | ActiveRecord: 3.1ms | Allocations: 18645) Workaround: - Use hammer CLI to unset content_default_http_proxy hammer> settings set --name content_default_http_proxy --value ""