Hi Ryan,
This appears to have fixed the nvme partition problem but, I'm sure
there are nicer ways to do it.
root@maas1:~# diff -u
/usr/lib/python3/dist-packages/curtin/commands/block_meta.py
/usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig
--- /usr/lib/python3/dist-packages/curtin/commands/block_meta.py
2016-03-07 23:37:34.137946135 +0000
+++ /usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig
2016-03-07 23:37:28.565864667 +0000
@@ -368,13 +368,7 @@
partnumber = determine_partition_number(vol.get('id'), storage_config)
disk_block_path = get_path_to_storage_volume(vol.get('device'),
storage_config)
-
- if disk_block_path == '/dev/nvme0n1':
- volume_path = disk_block_path + 'p' + str(partnumber)
- else
- volume_path = disk_block_path + str(partnumber)
-
+ volume_path = disk_block_path + str(partnumber)
devsync_vol = os.path.join(disk_block_path)
elif vol.get('type') == "disk":
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401190
Title:
curtin makes assumptions about partition names on all devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
