Thanks for filing the bug.
A "quickfix" would involve getting into the installer shell, manually
patching the curtin python source on the instance, and then re-running
the install. I've not poked around inside the installer so I'm not sure
where the the subiquity snap keeps curtin. If you do find it then you
can apply this change:
The line change needed for curtin to match the WWID of the nvme device:
diff --git a/curtin/block/schemas.py b/curtin/block/schemas.py
index fb7507d..96b3eb6 100644
--- a/curtin/block/schemas.py
+++ b/curtin/block/schemas.py
@@ -135,7 +135,8 @@ DISK = {
'type': 'string',
'oneOf': [
{'pattern': r'^0x(\d|[a-zA-Z])+'},
- {'pattern': r'^nvme\.(\d|[a-zA-Z]-)+'}],
+ {'pattern': r'^(nvme|eui)+\.(\d|[a-zA-Z]|\-)+'},
+ ],
},
'grub_device': {
'type': ['boolean', 'integer'],
I'm putting but a branch to fix this pattern and when it his curtin
master, when the subiquity snap is rebuilt and published, then the
installer will pick up the fix as well.
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841321
Title:
Curtin Fails to Validate Storage Config with Crucial P1 NVMe drive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1841321/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
