Allow registration when host is unregistered and DMI UUID has changed - Error: This host is reporting a DMI UUID that differs from the existing registration
Steps to test:
1. Register a content host to a satellite
2. Unregister it
3. Create a file with the content host's DMI UUID in it: echo '{"dmi.system.uuid": "this-is-made-up"}' > /etc/rhsm/facts/uuid.facts
4. Reregister it to see that it works
5. Unregister content host
6. change the content host's DMI UUID: echo '{"dmi.system.uuid": "another-made-up"}' > /etc/rhsm/facts/uuid.facts
7. Reregister content host
Expected result:
Successfully registers host
Actual result:
Successfully registers host
Note, you can update the DMI UUID multiple times and unregister and reregister the content host as you see fit. It will pass every time.
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
Steps to test: 1. Register a content host to a satellite 2. Unregister it 3. Create a file with the content host's DMI UUID in it: echo '{"dmi.system.uuid": "this-is-made-up"}' > /etc/rhsm/facts/uuid.facts 4. Reregister it to see that it works 5. Unregister content host 6. change the content host's DMI UUID: echo '{"dmi.system.uuid": "another-made-up"}' > /etc/rhsm/facts/uuid.facts 7. Reregister content host Expected result: Successfully registers host Actual result: Successfully registers host Note, you can update the DMI UUID multiple times and unregister and reregister the content host as you see fit. It will pass every time. Marking issue as verified. Tested on 6.5.3 snap 1.