Bug 1756056 - 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
Summary: Allow registration when host is unregistered and DMI UUID has changed - Error...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 6.5.3
Assignee: Jonathon Turel
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-26 16:42 UTC by Mike McCune
Modified: 2019-10-29 17:22 UTC (History)
21 users (show)

Fixed In Version: tfm-rubygem-katello-3.10.0.58-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1747177
Environment:
Last Closed: 2019-10-29 17:21:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27739 0 Normal Closed Allow registration when host is unregistered and DMI UUID has changed 2020-09-04 07:47:36 UTC
Red Hat Product Errata RHBA-2019:3241 0 None None None 2019-10-29 17:22:02 UTC

Comment 3 Lai 2019-10-07 19:02:49 UTC 
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.
Comment 5 errata-xmlrpc 2019-10-29 17:21:50 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.