Description of problem:
Version-Release number of selected component (if applicable):
Build: Satellite 6.4.0 snap11
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,
This disassociates the host from the compute resource
It should not disassociate the host and edit them successfully
The bug blocks Vmware hot add functions and will also block other VM related actions for all other compute resources
Upstream bug assigned to firstname.lastname@example.org
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.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23373 has been resolved.
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
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.