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.
Created attachment 1745583[details]
screenshot of issue
Description of problem:
unable to clear http_proxy_except_list setting ones set.
Version-Release number of selected component (if applicable):
- Satellite 6.9.0 snap 8
How reproducible:
- Always
Steps to Reproduce:
1. Go to Administer > Settings
2. Update "HTTP(S) proxy except hosts" field. (Add anything)
3. Try to clear "HTTP(S) proxy except hosts" field.
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:
- No error, successfully able to clear the field data.
Additional info:
2021-01-08T07:54:53 [I|app|d3f36969] Started PUT "/api/settings/93" for 127.0.0.1 at 2021-01-08 07:54:53 -0500
2021-01-08T07:54:53 [I|app|d3f36969] Processing by Api::V2::SettingsController#update as JSON
2021-01-08T07:54:53 [I|app|d3f36969] Parameters: {"setting"=>{"value"=>"[FILTERED]"}, "apiv"=>"v2", "id"=>"93"}
2021-01-08T07:54:53 [D|tax|d3f36969] Current location set to BJISZOkXIn
2021-01-08T07:54:53 [D|tax|d3f36969] Current organization set to woJnlPH
2021-01-08T07:54:53 [E|app|d3f36969] Unprocessable entity Setting::General (id: 93):
d3f36969 | Value must be comma separated
d3f36969 |
2021-01-08T07:54:53 [I|app|d3f36969] Rendering api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout
2021-01-08T07:54:53 [I|app|d3f36969] Rendered api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout (Duration: 4.3ms | Allocations: 6685)
2021-01-08T07:54:53 [D|app|d3f36969] Body: {
d3f36969 | "error": {"id":93,"errors":{"value":["must be comma separated"]},"full_messages":["Value must be comma separated"]}
d3f36969 | }
d3f36969 |
2021-01-08T07:54:53 [I|app|d3f36969] Completed 422 Unprocessable Entity in 19ms (Views: 7.3ms | ActiveRecord: 1.4ms | Allocations: 19654)
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
Created attachment 1745583 [details] screenshot of issue Description of problem: unable to clear http_proxy_except_list setting ones set. Version-Release number of selected component (if applicable): - Satellite 6.9.0 snap 8 How reproducible: - Always Steps to Reproduce: 1. Go to Administer > Settings 2. Update "HTTP(S) proxy except hosts" field. (Add anything) 3. Try to clear "HTTP(S) proxy except hosts" field. 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: - No error, successfully able to clear the field data. Additional info: 2021-01-08T07:54:53 [I|app|d3f36969] Started PUT "/api/settings/93" for 127.0.0.1 at 2021-01-08 07:54:53 -0500 2021-01-08T07:54:53 [I|app|d3f36969] Processing by Api::V2::SettingsController#update as JSON 2021-01-08T07:54:53 [I|app|d3f36969] Parameters: {"setting"=>{"value"=>"[FILTERED]"}, "apiv"=>"v2", "id"=>"93"} 2021-01-08T07:54:53 [D|tax|d3f36969] Current location set to BJISZOkXIn 2021-01-08T07:54:53 [D|tax|d3f36969] Current organization set to woJnlPH 2021-01-08T07:54:53 [E|app|d3f36969] Unprocessable entity Setting::General (id: 93): d3f36969 | Value must be comma separated d3f36969 | 2021-01-08T07:54:53 [I|app|d3f36969] Rendering api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout 2021-01-08T07:54:53 [I|app|d3f36969] Rendered api/v2/errors/unprocessable_entity.json.rabl within api/v2/layouts/error_layout (Duration: 4.3ms | Allocations: 6685) 2021-01-08T07:54:53 [D|app|d3f36969] Body: { d3f36969 | "error": {"id":93,"errors":{"value":["must be comma separated"]},"full_messages":["Value must be comma separated"]} d3f36969 | } d3f36969 | 2021-01-08T07:54:53 [I|app|d3f36969] Completed 422 Unprocessable Entity in 19ms (Views: 7.3ms | ActiveRecord: 1.4ms | Allocations: 19654)