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.
Rahul, you already had/have similar bug on your place, would you mind fixing this one as well? I promise quick review, ping me please. Thanks!
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,
*** Bug 1919565 has been marked as a duplicate of this bug. ***
Upstream bug assigned to afeferku
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31798 has been resolved.
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
*** Bug 1925193 has been marked as a duplicate of this bug. ***