MAAS is unable to handle duplicate UUIDs

Bug #1893690 reported by Lee Trager
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fix Released
Lee Trager
Fix Released

Bug Description

While the hardware universal unique identifier is supposed to be unique it appears Dell firmware has a bug where they use the service number for the UUID which is not unique. This causes commissioning to fail as MAAS has a database constraint that the UUID must be unique.

The purpose of collecting the UUID is because some hardware, such as IBM Z series LPARs, only identify themselves with the UUID. PXELinux(legacy BIOS booting) also sends the UUID to MAAS before sending the MAC address when requesting boot config. MAAS can still function without knowing the UUID if the firmware supports being identified by MAC address.

MAAS can detect duplicate UUID's and remove them to work around this firmware bug.

Tags: ps5

Related branches

Changed in maas:
milestone: none → next
status: In Progress → Fix Committed
Changed in maas:
milestone: next → 2.9.0b4
Lee Trager (ltrager)
Changed in maas:
status: Fix Committed → Fix Released
Revision history for this message
Nobuto Murata (nobuto) wrote :

Subscribing ~field-high. We are hit by the "Node with this Hardware uuid already exists" issue with one of the servers we are using for a field deployment (to clarify it's not Dell).

Revision history for this message
Nobuto Murata (nobuto) wrote :

Excerpt of lshw just for the reference:

Revision history for this message
Nobuto Murata (nobuto) wrote :

Just for the record, a workaround I used was updating Postgres directly like:

UPDATE maasserver_node SET hardware_uuid=NULL WHERE hardware_uuid='03000200-0400-0500-0006-000700080009';

Nobuto Murata (nobuto)
tags: added: ps5
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.