Bogus serial string in subiquity install wwn-eui.*
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
High
|
Unassigned | ||
curtin (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
subiquity (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Curtin has been given (or maybe generated for subiquity) a storage config which includes a serial value with wwn prefixing the actual serial (eui-XXXXX). This results if failure to find the disk since the wwn prefix is not needed.
---
curtin: Installation started. (19.2)
start: cmd-install/
get_path_
devsync for /dev/disk/
Running command ['partprobe', '/dev/disk/
Error: Could not stat device /dev/disk/
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED udevadm_settle(): 0.006
Waiting on device path: /dev/disk/
Related branches
- Chad Smith: Approve
- Server Team CI bot: Approve (continuous-integration)
- Dan Watkins (community): Approve
-
Diff: 210 lines (+127/-14)4 files modifiedcurtin/commands/block_meta.py (+8/-12)
tests/unittests/test_block.py (+26/-0)
tests/unittests/test_commands_block_meta.py (+90/-1)
tests/unittests/test_curthooks.py (+3/-1)
Changed in curtin: | |
importance: | Undecided → High |
status: | New → Fix Committed |
Curtin is prefixing 'wwn' for configs which specify a wwn value. The wwn value does not include the string 'wwn' and udev rules for persistent disks prefix the wwn with wwn-<WWN value).
However, for NVME, udev may export ID_WWN=eui.XXXX value, and it may well be a WWN, it does not get symlinked as a wwn-<WWN> symlink in /dev/disk/by-id at all.