Bug 1889564

Summary:	Updating hostgroup of the host through bulk action allows blank lifecycle and blank content view of the hostgroup but not while updating individual host from Satellite Web UI.
Product:	Red Hat Satellite	Reporter:	shisingh
Component:	Hosts - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Shweta Singh <shwsingh>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	inecas, kgaikwad, oezr, vijsingh
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:01:59 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 shisingh 2020-10-20 02:14:45 UTC

Description of problem:

When we try to update the hostgroup of multiple hosts using bulk action it allows us to change the association even if hostgroup does not have any Life Cycle Environment or Content View associated.

Whereas if we try to update the host: Host >> All Hosts >> Edit >> Change the Hostgroup >> Make sure that Content View and LifeCycle Environment is blank >> Submit, it fails with below mentioned error message:

===============================
  Content view can't be blank
  Lifecycle environment can't be blank
===============================


Version-Release number of selected component (if applicable): Red Hat Satellite 6.7 and Red Hat Satellite 6.8


How reproducible: Everytime


Steps to Reproduce:

1. Create a Hostgroup test_blank and keep everything blank.

2. Try to change the hostgroup of any host using the steps: On Satellite Web UI, navigate to Hosts >> All Hosts >> Select Hosts >> From the drop down menu, select Change Group >> Select the Host Group and Submit. Change will be performed irrespective of the fact that Host group is blank.

3. Now try to change the hostgroup of another host using the steps: On Satellite Web UI, navigate to Hosts >> All Hosts >> Select Host >> Edit >> Change the Hostgroup >> Make sure that Life Cycle and Content View is blank >> Submit.

Note: Known bug : Changing HostGroup does not reload Lifecycle or content View from the HostGroup #1888523


Actual results: It fails to change the hostgroup with below mentioned error:

===============================
  Content view can't be blank
  Lifecycle environment can't be blank
===============================


Expected results: It should either change the hostgroup or it should fail for both the methods mentioned in step 2 and step 3.


Additional info:

Comment 1 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 2 Brad Buckingham 2022-09-02 20:31:26 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 4 Brad Buckingham 2022-10-28 18:01:59 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.