Bug 1989706

Summary:	If we set the null value in the discovery host, it generates the "something went wrong form" alert however "can't be blank "message is already displayed on the setting update form.
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Settings	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shweta Singh <shwsingh>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	apatel, bbuckingham, mhulan
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-10-28 18:05:34 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 2021-08-03 18:32:02 UTC

Description of problem: If we set the empty value in the discovery host, it generates the "something went wrong..." alert however "can't be blank" alert is already displayed on the setting update form.


Version-Release number of selected component (if applicable):
6.10

How reproducible:
always

Steps to Reproduce:
1. Install satellite using 6.10.
2. go to -> settings ->discovery_hostname
3. Set the empty value, we get the alert "can't be blank" on the update form that is correct but in parallel, we get "Oh no! Something went wrong while submitting the form, the server returned the following error: Value can't be blank" alert message, I think that should not come.

Actual results:
"Oh no! Something went wrong while submitting the form, the server returned the following error: Value can't be blank" error message popped up, however "can't be blank" is already in the setting update form

Expected results:
"Oh no! Something went wrong while submitting the form, the server returned the following error: Value can't be blank" error message should not be come if the alert "can't be blank" is already in the discovery_hostname settings form

Additional info:

Comment 3 Leos Stejskal 2022-07-19 13:03:13 UTC

Created redmine issue https://projects.theforeman.org/issues/35242 from this bug

Comment 4 Brad Buckingham 2022-09-02 20:25:18 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 5 Brad Buckingham 2022-09-02 20:30:51 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Shweta Singh 2022-10-14 07:52:16 UTC

@bbuckingham This issue is fixed in 6.11.z and 6.12. Can we move this BZ to verified as it is blocking a negative scenario in automation?

Comment 7 Brad Buckingham 2022-10-28 18:05:34 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 8 Brad Buckingham 2022-12-09 18:09:42 UTC

Moving to closed:currentrelease based upon comment 6.