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: In settings, Failed to set the null value in the discovery_prefix.
Version-Release number of selected component (if applicable):
6.9
How reproducible:
always
Steps to Reproduce:
1. Login satellite through UI.
2. Go to Administrator-->Settings-->discovery_prefix
3. set null value but it gets failed with below error.
Oh no! Something went wrong while submitting the form, the server returned the following error: Error: Request failed with status code 422
Actual results:
Failed to set null value in the discovery_prefix.
Expected results:
Null value should be set
Additional info: In the earlier release, it was working.
Hello Devendra,
The value of discovery_prefix must not be set to null. Although, the error that is displayed is incorrect.
The error shown here should be 'Value can't be blank'. This error comes from react it seems. Let me take a closer look :)
Let me know if you disagree.
Thank you,
Verified on 6.9 Snap 15
Verifications point
1. Login satellite through UI.
2. Go to Administrator-->Settings-->discovery_prefix
3. The below valid error message is displayed if we set the discovery_prefix value as empty.
Oh no! Something went wrong while submitting the form, the server returned the following error: Value can't be blank
4- Verified the fixed package
# rpm -qa|grep ^foreman-2.3.1.1
foreman-2.3.1.11-1.el7sat.noarch
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