Bug 1749785 - [Sat6.5/Bug/Blocker] Registering multiple HPE MC990X servers fails due hardcoded consistent bios uuid [NEEDINFO]
Summary: [Sat6.5/Bug/Blocker] Registering multiple HPE MC990X servers fails due hardco...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
high
high with 1 vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2019-09-06 12:44 UTC by Oliver Falk
Modified: 2023-03-24 15:24 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-27 13:33:04 UTC
Target Upstream Version:
Embargoed:
peter.vreman: needinfo? (bkearney)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4396951 0 None None None 2019-12-09 13:05:23 UTC

Description Oliver Falk 2019-09-06 12:44:22 UTC
Description of problem:
MC990X servers seem to have a hardcoded BIOS UUID. Example from the customer env (some data has been marked with 'X')

# dmidecode -s system-uuid; hostname -s
8B2C9555-5C8E-4221-BF48-DFF30244XXXX
li-lc-XXXX

# dmidecode -s system-uuid; hostname -s
8B2C9555-5C8E-4221-BF48-DFF30244XXXX
chbbhilsvXXX

# dmidecode -s system-uuid; hostname -s
8B2C9555-5C8E-4221-BF48-DFF30244XXXX
li-lq-XXXX

Version-Release number of selected component (if applicable): 6.5.2.1


How reproducible: Always.

Steps to Reproduce (untested, but should do the trick):
1. Override UUID on host1:
   echo '{"virt.uuid": "4546B285-6C41-5D6R-86G5-0BFR4B3625FD"}' > /etc/rhsm/facts/virt_uuid.facts
2. Override the UUID on host2 (same as for host1):
   echo '{"virt.uuid": "4546B285-6C41-5D6R-86G5-0BFR4B3625FD"}' > /etc/rhsm/facts/virt_uuid.facts
3. Try to register host1 and host2 (second will fail)

Actual results:
While we believed that the BIOS UUID should be unique, unfortunately it may not be and therefore the recently introduced UUID check fails here.


Expected results:
UUID cannot be trusted as being as unique as we expected it and we should think about another solution.


Additional info:
Overriding the UUID with some other uuid (generated via uuidgen) works as a workaround for the moment. Customer case is going to be attached.

Comment 3 Oliver Falk 2019-09-06 13:25:28 UTC
Adding link to RHBZ#1742204 , as it seems to be pretty related.

Comment 13 Peter Vreman 2020-04-20 07:45:20 UTC
Bryan,

For me as user with MC990 the workaround to override the UUID in the facts with a random value as described in KB4396951 is simple and works.
I do not see the need for more support in Sat6.

For me this BZ can be closed based on the current documentation

Peter

Comment 15 Mike McCune 2020-07-27 13:33:04 UTC
We released an update in Satellite 6.7 that allows disabling of the UUID uniqueness constraint:

https://bugzilla.redhat.com/show_bug.cgi?id=1772199

How to use verify and use the new setting:

1. Added following configuration line to /etc/candlepin/candlepin.conf
    candlepin.use_system_uuid_for_matching=false

2. satellite-maintain serivce restart

3. Set the uuid to be the same on two hosts
    echo '{"virt.uuid": "4546B285-6C41-5D6R-86G5-0BFR4B3625FD", "virt.is_guest":"True"}' > /etc/rhsm/facts/virt_uuid.facts

4. Registered both hosts to the satellite


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