Red Hat Bugzilla – Bug 1287735
Compute resource is not updated when VM is moved from one vCenter to another
Last modified: 2017-01-09 00:06:20 EST
Description of problem:
When you move the VM between vCenter the "VMware" functionality like connecting to the console etc. is lost.
Version-Release number of selected component (if applicable):
6.0.8 and possibly all the newer one.
Create a VM on one hypervisor, install RHEL, register it in the satellite using virt-who. You should have the machine in the "Content hosts" and there should be a Compute resource associated with this machine. Now move the VM to another vCenter and. The virt-who should report the machine, in another vCenter, so the derived subscription has to be changed for this content host. At this moment the associated Compute resource is still not updated for the machine and the VMware functionality doesn't work.
The relation with Compute resource will be updated when the machine is reported from a different vCenter.
Customer was able to get the behavior back updating the database table hosts, column computed_resource to the correct id of the corresponding computed resource.
Moving 6.2 bugs out to sat-backlog.