Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
After renaming the hypervisor in /content_hosts and another run of virt-who
the hypervisor content host is again created with a random name but with
the same uuid.
Version-Release number of selected component (if applicable):
Satellite 6.2 SNAP 13.1
virt-who 0.14-9.el7
How reproducible:
With every virt-who run
Steps to Reproduce:
1. Register hypervisor via virt-who
2. Rename hypervisor in /content_hosts
3. Run virt-who again
Actual results:
A new entry is created in /content_hosts
Expected results:
Only update the already existing content host
Additional info:
- virt-who is always sending the correct hypervisor uuid
- looks like the unique identifier was changed from the content hosts uuid to the name
- this is a regression as it worked fine in 6.1
Note that the host name is not changed in candlepin, which I think is a good thing. In katello, when looking for existing hypervisors to match on the results returned from candlepin, the UUID needs to be searched for with the fallback being the name.
This situation will lead to corrupt database since there will be multiple hosts referencing a single candlepin consumer. If the consumer is deleted (ie. one of the hosts is deleted) then the other records will fail w/ errors when queried.
Verified with sat62 GA snap18.1
I registered rhev hypervisor with satellite62 server and later changed the content-host name from "virt-who-rhevh2-1" to "rhevh2". Content host was successfully renamed after running virt-who without another duplicate entry.
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/RHBA-2016:1501