Bug 1600540

Summary:	Editing a host will disassociate the host from compute resource
Product:	Red Hat Satellite	Reporter:	Sanket Jagtap <sjagtap>
Component:	Compute Resources	Assignee:	Shira Maximov <mshira>
Status:	CLOSED ERRATA	QA Contact:	Sanket Jagtap <sjagtap>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	egolov, kbidarka, mhulan, oprazak, orabin
Target Milestone:	6.4.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-1.18.0.6-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 18:57:57 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 Sanket Jagtap 2018-07-12 13:03:07 UTC

Description of problem:


Version-Release number of selected component (if applicable):
Build: Satellite 6.4.0 snap11

How reproducible:
Always

Steps to Reproduce:
1. Create a Host on  compute resource,
2. After creating the host , Go to edit host , and try to edit the host and hit submit,
3.

Actual results:
This disassociates the host from the compute resource

Expected results:
It should not disassociate the host and edit them successfully

Additional info:
No error

Comment 2 Sanket Jagtap 2018-07-12 13:08:32 UTC

The bug blocks Vmware hot add functions and will also block other VM related actions for all other compute resources

Comment 3 Satellite Program 2018-07-12 16:26:02 UTC

Upstream bug assigned to mshira

Comment 4 Satellite Program 2018-07-12 16:26:07 UTC

Upstream bug assigned to mshira

Comment 5 orabin 2018-07-12 17:52:17 UTC

This happens when the host is connected to a hostgroup and instead of using the hostgroup's compute resource "inherit" is clicked and a different compute resource is selected.

The workaround for now is to avoid a hostgroup or use a hostgroup with the compute resource and not change it on the host.
In this snap using the hostgroup with compute resource selected gives an error. That is fixed in: https://bugzilla.redhat.com/show_bug.cgi?id=1572973 and then the workaround can be used until this bug is fixed.

Comment 6 Satellite Program 2018-07-20 12:26:36 UTC

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

Comment 8 Sanket Jagtap 2018-08-31 08:42:46 UTC

Build: Satellite 6.4.0 snap 19 

I am able to edit the host created successfully.

Followed the steps from #c5. 

Host is not disassociated after editing and changes are done successfully

Comment 9 Bryan Kearney 2018-10-16 18:57:57 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, 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-2018:2927