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:
Client registration fails with
HTTP error (422 - Unknown): This host is reporting a DMI UUID that differs from the existing registration
Run the following query by UUID on Satellite and found the same id registered with a different host.
# echo "select h.name,h.id,fv.host_id,fv.id,fv.value from fact_values as fv, hosts as h where value='UUID' and h.id=fv.host_id" | su - postgres -c "psql foreman"
changing UUID helps but need to identify why hotfix didn't work
satellite-6.5.2.1-1.el7sat.noarch
Actual results:
cannot subscribe a client to Satellite during the build of a new host.
Installed the hotfix mentioned BZ1747177
tfm-rubygem-katello-3.10.0.55-3.HOTFIXBZ17422041747177.el7sat.noarch
But the result still the same.
Expected results:
Additional info:
this is the same bug as BZ1747177, closing as a dupe. If you see slightly different behavior, please comment in that bug.
*** This bug has been marked as a duplicate of bug 1747177 ***