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.
Steps to test:
1. Register a client to satellite.
2. Run sub-man clean
3. Change hostname (hostnamectl set-hostname something)
4. Reregister to see failure
5. Run sub-man facts | grep dmi.system.uui to grab the uuid from the client
6. Go to Administer -> settings and search for 'Host Duplicate DMI UUIDs'
7. Add the uuid taken from 5 to 'Host Duplicate DMI UUIDs' in the form of an array
8. Reregister client
9. Hosts -> All Hosts -> <client name> -> facts -> dmi -> systems
10. Verify that UUID in systems is different from client
Expected:
Client UUID: another-abcd (From step 5)
System UUID: 617cba4f-6e79-4e0e-a16c-c8e0188d9bbd (step 9)
Actual:
Client UUID: another-abcd (From step 5)
System UUID: 617cba4f-6e79-4e0e-a16c-c8e0188d9bbd (step 9)
You can see that the client's uuid and the system's uuid are different which is what is intended.
Marking issue as verified.
Tested on 6.5.3 snap 1.
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-2019:3241