MAAS is unable to handle duplicate UUIDs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Lee Trager | ||
| 2.8 |
Fix Released
|
Undecided
|
Unassigned | ||
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.
https:/
https:/
https:/
Related branches
- Lee Trager (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 75 lines (+42/-3)2 files modifiedsrc/metadataserver/builtin_scripts/hooks.py (+26/-3)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+16/-0)
- MAAS Lander: Approve
- Dougal Matthews (community): Approve
-
Diff: 75 lines (+42/-3)2 files modifiedsrc/metadataserver/builtin_scripts/hooks.py (+26/-3)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+16/-0)
| Changed in maas: | |
| milestone: | none → next |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | next → 2.9.0b4 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| Nobuto Murata (nobuto) wrote | #1 |
| Nobuto Murata (nobuto) wrote | #2 |
| Nobuto Murata (nobuto) wrote | #3 |
| tags: | added: ps5 |
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).