Bug 1747177 - 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 [NEEDINFO]
Summary: Allow registration when host is unregistered and DMI UUID has changed - Error...
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
medium with 6 votes vote
Target Milestone: 6.6.0
Assignee: Jonathon Turel
QA Contact: Lai
: 1754596 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2019-08-29 20:04 UTC by Jonathon Turel
Modified: 2020-01-08 17:02 UTC (History)
23 users (show)

Fixed In Version: rubygem-katello-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1756056 (view as bug list)
Last Closed: 2019-10-22 12:47:58 UTC
Target Upstream Version:
ekirby: needinfo? (bkearney)

Attachments (Terms of Use)
tfm-rubygem-katello- (11.66 MB, application/x-rpm)
2019-09-12 20:28 UTC, Mike McCune
no flags Details

System ID Priority Status Summary Last Updated
Foreman Issue Tracker 27739 Normal Closed Allow registration when host is unregistered and DMI UUID has changed 2020-01-17 17:57:35 UTC
Red Hat Knowledge Base (Solution) 4450981 None None None 2019-09-27 23:18:47 UTC
Red Hat Product Errata RHSA-2019:3172 None None None 2019-10-22 12:48:06 UTC

Description Jonathon Turel 2019-08-29 20:04:34 UTC
If a host is unregistered and its DMI UUID has changed by the next time it attempts to register (but the hostname is the same) it will not work. It should work so long as the DMI UUID is unique and the host record on the server is not already registered.

Comment 1 Jonathon Turel 2019-08-29 20:04:36 UTC
Created from redmine issue https://projects.theforeman.org/issues/27739

Comment 2 Jonathon Turel 2019-08-29 20:04:38 UTC
Upstream bug assigned to jturel@redhat.com

Comment 4 Mike McCune 2019-09-05 17:05:24 UTC
This is seen during registration when subscription-manager returns the error:

HTTP error (422 - Unknown): This host is reporting a DMI UUID that differs from the existing registration.

Comment 9 Jean Paul Gatt 2019-09-10 09:36:51 UTC

We are experiencing the same issue. We have satellite registering Virtual machines provisioned in openstack. We keep hitting the error:

"HTTP error (422 - Unknown): This host is reporting a DMI UUID that differs from the existing registration.".

Error was introduced when upgrading from 6.4 to 6.5. Running on

Can you suggest a fix?

This has destroyed the ability of clients to create and destroy their machines on demand.

Comment 14 Mike McCune 2019-09-12 20:24:37 UTC
*** Satellite Hotfix Available ***

1) Download tfm-rubygem-katello- from this bugzilla to your Satellite

2) Install:

rpm -Uvh tfm-rubygem-katello-

3) restart:

satellite-maintain service restart

4) resume operations

Comment 15 Mike McCune 2019-09-12 20:28:51 UTC
Created attachment 1614654 [details]

Comment 16 Greg Procunier 2019-09-13 16:45:26 UTC
3 successful re-deploys, however I just got a new error .. not sure if its related but it occurs right after loading the katello-ca-consumer-latest and running the re-registration.

HTTP error (400 - Bad Request): Problem creating unit ConsumerDTO [uuid: e85efceb-f79e-4b0d-81eb-59551fa0736e, name: cfme-database-0.idm.example.com, owner id: null]

Comment 17 Bernd Nies 2019-09-16 08:43:58 UTC
Having the same issue after updating from Satellite 6.5.1 to last thursday.

Comment 18 Lai 2019-09-18 19:36:00 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.6.0 snap 21

Comment 19 Jean Paul Gatt 2019-09-20 07:38:35 UTC

About the steps to test ... those would have worked even pre-patch, because a 'subscription-manager unregister' cleans up the instance from satellite (it was our work around)'

However, deleting the instance or doing a 'subscription-manager clean' would only delete the local copy of the registration, and would probabbly cause the previous bug to be triggered.

I should not that with this patch, the issue seems to have been mitigated.

Maybe a 'dirty' deletion example should be included in the automated build testing to avoid this bug springing up again.

Comment 22 Mike McCune 2019-09-23 23:44:30 UTC
*** Bug 1754596 has been marked as a duplicate of this bug. ***

Comment 24 errata-xmlrpc 2019-10-22 12:47:58 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.


Note You need to log in before you can comment on or make changes to this bug.