Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1287735 - Compute resource is not updated when VM is moved from one vCenter to another
Summary: Compute resource is not updated when VM is moved from one vCenter to another
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.0.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-02 14:46 UTC by Marcel Gazdík
Modified: 2020-09-10 09:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:04:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marcel Gazdík 2015-12-02 14:46:38 UTC 
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.

How reproducible:
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.


Expected results:
  The relation with Compute resource will be updated when the machine is reported from a different vCenter.


Additional info:
  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.
Comment 2 Bryan Kearney 2016-08-04 20:12:41 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 5 Bryan Kearney 2018-09-04 18:04:38 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Note You need to log in before you can comment on or make changes to this bug.