Bug 1911228

Summary:	In the settings, Failed to set null value in the discovery_prefix.
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Settings	Assignee:	Amir <afeferku>
Status:	CLOSED ERRATA	QA Contact:	Devendra Singh <desingh>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	aagrawal, apatel, gpayelka, lzap, mhulan, oezr
Target Milestone:	6.9.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	foreman-2.3.1.10-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-21 13:25:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Devendra Singh 2020-12-28 09:29:10 UTC

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.

Comment 1 Lukas Zapletal 2021-01-19 10:35:23 UTC

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!

Comment 3 Rahul Bajaj 2021-01-28 10:05:09 UTC

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,

Comment 6 Ondřej Ezr 2021-02-17 14:32:14 UTC

*** Bug 1919565 has been marked as a duplicate of this bug. ***

Comment 7 Bryan Kearney 2021-02-17 16:00:37 UTC

Upstream bug assigned to afeferku

Comment 8 Bryan Kearney 2021-02-17 16:00:39 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31798 has been resolved.

Comment 10 Devendra Singh 2021-02-25 14:42:36 UTC

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

Comment 13 errata-xmlrpc 2021-04-21 13:25:01 UTC

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

Comment 14 Tomer Brisker 2021-05-06 07:49:39 UTC

*** Bug 1925193 has been marked as a duplicate of this bug. ***