Bug 1749785
| Summary: | [Sat6.5/Bug/Blocker] Registering multiple HPE MC990X servers fails due hardcoded consistent bios uuid | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Oliver Falk <ofalk> |
| Component: | Registration | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Stephen Wadeley <swadeley> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.5.0 | CC: | bkearney, igreen, jturel, ktordeur, mkalyat, mmccune, peter.vreman, vgunasek, vmeghana |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-27 13:33:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1122832 | ||
Adding link to RHBZ#1742204 , as it seems to be pretty related. 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 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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |
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.