Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices
On Mon, Mar 7, 2016 at 5:40 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi Ryan,
>
> This appears to have fixed the nvme partition problem but, I'm sure
> there are nicer ways to do it.
>
>
Hi Rob!
Thanks for confirming a workaround.
> 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 +
> +++ /usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig
> 2016-03-07 23:37:28.565864667 +
> @@ -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 subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> 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
>
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices
On Mon, Mar 7, 2016 at 1:50 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi Ryan,
>
> Thanks, let me know if you need me to make any changes or run through
> any tests.
>
> A quick question if I may: How is the config generated when the node is
> deploying? I have found that storage config in curtin_userdata on the
> maas server appears to be ignored or clobbered e.g.
>
If you're using maas 1.8, or maas 1.9; maas itself is generating storage
configuration
https://maas.ubuntu.com/docs/storage.html#storage
Ideally you don't need to inject your own custom partitioning/storage
config; you
configure maas in the UI and it emits storage configuration to curtin.
It's not clear to me how you're combining your own user-data with what MaaS
supplies.
> If I execute: /var/lib/cloud/instance/scripts/part-001 # fails due to bug
> cd curtin
> cat configs/config-000.cfg # I see the storage config I have set on the
> maas server in curtin_userdata
>
> #cloud-config
> ...
> ...
>
> partitioning_commands:
> builtin: [curtin, block-meta, custom]
> storage:
> config:
> - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
> - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 1, offset:
> 4194304B, size: 128026935296B, type: partition, wipe: superblock}
> - {fstype: ext4, id: nvme0n1p1_format, label: 'rootfs', type: format,
> path: /dev/nvme0n1p1, volume: nvme0n1p1}
> version: 1
>
> cat configs/config-002.cfg # appears to be the device(s) that are found
> during commissioning
>
> partitioning_commands:
> builtin: [curtin, block-meta, custom]
> storage:
> config:
> - {grub_device: true, id: sdc, model: Samsung SSD 840, name: sdc,
> ptable: gpt, serial: S1D9NSAFB19195M,
> type: disk, wipe: superblock}
> - {device: sdc, id: sdc-part1, name: sdc-part1, number: 1, offset:
> 4194304B, size: 1000198897664B,
> type: partition, uuid: 8bcce503-ad8f-495e-a158-669829585db2, wipe:
> superblock}
> - {fstype: ext4, id: sdc-part1_format, label: '', type: format, uuid:
> 0195af9d-764d-4b35-8e53-07573aa4c057,
> volume: sdc-part1}
> - {device: sdc-part1_format, id: sdc-part1_mount, path: /, type: mount}
> version: 1
> ...
> ...
>
>
> I was trying to test an install to one of the other disks which also
> failed.
>
It's hard to say; if you have the entire curtin config sent I may be able
to parse out what's going on:
>From the maas cli:
maas node get-curtin-config
and attach to this bug.
>
> I had to remove the nvme device and 2 other devices from the web ui as
> configs/config-002.cfg had every disk listed, including the nvme device
> which I had specified in curtin_userdata. The config data is that from
> commissioning.
>
> I also noted that despite me selecting a different boot device that it
> was still trying to install grub to sda.
>
>
> Does this sound like another bug with curtin or should I raise it with
> the maas project?
>
Boot device selection *could* be a maas issue or curtin. I suggest
opening a new bug against MAAS for the boot device selection,
and I can add a MAAS task to this one. In both places, please append
the output from the maas get-curtin-config output attached. This helps
us debug whether MAAS sent curtin valid configuration and determine
if we need to fix the bug in MAAS or curtin itself.
In _this_ bugs case; if the config you send which defines 'number' field in
the partition dictionary, then curtin will *faithfully* attempt to use
directly; ie; curtin is doing what it was told.
In the case where 'number' is not defined, curtin will attempt to determine
the
correct partition number. For NVME devices, the logic is not sufficient
since
it doesn't really know that the underlying device is an NVME and NVME
devices
use different scheme for naming partition device entries (p vs.
just )
In this bug, we will teach curtin to detect NVME devices and pick the
correct partition dev path
if the config does _NOT_ include a specified 'number' value.
I'll open a MAAS task in this bug to help track if MAAS itself needs to
know a device is an NVME
and then specify the 'number' differently ('p1' vs '1').
--
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> 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
>
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify
Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices
On Mon, Mar 7, 2016 at 2:15 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi Ryan,
>
> Here you go
>
> /var/lib/cloud/instance/scripts/part-001 extract
>
> cd curtin
>
> cat configs/config-000.cfg
> #cloud-config
> …
> ...
> partitioning_commands:
> builtin: [curtin, block-meta, custom]
> storage:
> config:
> - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
> - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 'p1',
> offset: 4194304B, size: 128026935296B, type: partition, wipe: superblock}
> - {fstype: ext4, id: nvme0n1p1_format, label: 'rootfs', type: format,
> path: /dev/nvme0n1p1, volume: nvme0n1p1}
> version: 1
>
> bin/curtin --showtrace --install-deps install
> --config=configs/config-000.cfg
> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
> Creating new GPT entries.
> The operation has completed successfully.
> An error occured handling 'nvme0n1p1': IOError - [Errno 2] No such file or
> directory: '/sys/block/nvme0n1/nvme0n1None/size'
> Traceback (most recent call last):
> File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
> File "curtin/commands/block_meta.py", line 62, in block_meta
> meta_custom(args)
> File "curtin/commands/block_meta.py", line 1083, in meta_custom
> handler(command, storage_config_dict)
> File "curtin/commands/block_meta.py", line 565, in partition_handler
> with open(os.path.join(previous_partition, "size"), "r") as fp:
> IOError: [Errno 2] No such file or directory:
> '/sys/block/nvme0n1/nvme0n1None/size'
> [Errno 2] No such file or directory: '/sys/block/nvme0n1/nvme0n1None/size'
> Installation failed with exception: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nAn error occured handling \'nvme0n1p1\': IOError - [Errno 2]
> No such file or directory:
> \'/sys/block/nvme0n1/nvme0n1None/size\'\nTraceback (most recent call
> last):\n File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in
> main\nret = args.func(args)\n File "curtin/commands/block_meta.py",
> line 62, in block_meta\nmeta_custom(args)\n File
> "curtin/commands/block_meta.py", line 1083, in meta_custom\n
> handler(command, storage_config_dict)\n File
> "curtin/commands/block_meta.py", line 565, in partition_handler\nwith
> open(os.path.join(previous_partition, "size"), "r") as fp:\nIOError: [Errno
> 2] No such file or directory:
> \'/sys/block/nvme0n1/nvme0n1None/size\'\n[Errno 2] No such file or
> directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n'
> Stderr: ''
> Traceback (most recent call last):
> File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
> File "curtin/commands/install.py", line 399, in cmd_install
> raise e
>
OK, no need to let you continue to debug getting curtin partition handling
to learn about NVME.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices
One more try, lets specify the partition "number" as 'p1' instead.
- {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 'p1', offset:
4194304B, size: 128026935296B, type: partition, uuid:
e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
On Mon, Mar 7, 2016 at 1:24 PM, Ryan Harper
wrote:
> OK; thanks. I need to work with nvme devices on Xenial; it looks like
> the storage naming rules for partitions are different for NVME devices (p1,
> p2, p3) versus other disks (1, 2, 3 4);
>
>
> On Mon, Mar 7, 2016 at 12:54 PM, Rob Sanderson <1401...@bugs.launchpad.net
> > wrote:
>
>> Hi Ryan,
>>
>> I have tried that but no luck.
>>
>> Config using curtin defaults:
>>
>> --
>> cat configs/config-002.cfg
>>
>> partitioning_commands:
>> builtin: [curtin, block-meta, custom]
>> storage:
>> config:
>> - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
>> disk, wipe: superblock}
>> - {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1,
>> offset: 4194304B, size: 128026935296B, type: partition, uuid:
>> e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
>> - {fstype: ext4, id: nvme0n1-part1_format, label: 'rootfs', type:
>> format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877, volume: nvme0n1-part1,
>> path: /dev/nvme0n1p1}
>> - {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /,
>> type: mount}
>> version: 1
>>
>> bin/curtin --showtrace --install-deps install
>> --config=configs/config-002.cfg
>>
>>
>> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
>> Creating new GPT entries.
>> The operation has completed successfully.
>> The operation has completed successfully.
>> An error occured handling 'nvme0n1-part1_format': ValueError -
>> '/dev/nvme0n11': no such file or directory
>> Traceback (most recent call last):
>> File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
>> ret = args.func(args)
>> File "curtin/commands/block_meta.py", line 62, in block_meta
>> meta_custom(args)
>> File "curtin/commands/block_meta.py", line 1083, in meta_custom
>> handler(command, storage_config_dict)
>> File "curtin/commands/block_meta.py", line 672, in format_handler
>> mkfs.mkfs_from_config(volume_path, info)
>> File "curtin/block/mkfs.py", line 207, in mkfs_from_config
>> label=info.get('label'))
>> File "curtin/block/mkfs.py", line 145, in mkfs
>> raise ValueError("'%s': no such file or directory" % path)
>> ValueError: '/dev/nvme0n11': no such file or directory
>> '/dev/nvme0n11': no such file or directory
>> Installation failed with exception: Unexpected error while running
>> command.
>> Command: ['curtin', 'block-meta', 'custom']
>> Exit code: 3
>> Reason: -
>> Stdout: 'Creating new GPT entries.\nThe operation has completed
>> successfully.\nThe operation has completed successfully.\nAn error occured
>> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
>> file or directory\nTraceback (most recent call last):\n File
>> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
>> args.func(args)\n File "curtin/commands/block_meta.py", line 62, in
>> block_meta\nmeta_custom(args)\n File "curtin/commands/block_meta.py",
>> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
>> File "curtin/commands/block_meta.py", line 672, in format_handler\n
>> mkfs.mkfs_from_config(volume_path, info)\n File "curtin/block/mkfs.py",
>> line 207, in mkfs_from_config\nlabel=info.get(\'label\'))\n File
>> "curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
>> such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such
>> file or directory\n\'/dev/nvme0n11\': no such file or directory\n'
>> Stderr: ''
>> Traceback (most recent call last):
>> File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
>> ret = args.func(args)
>> File "curtin/commands/install.py", line 399, in cmd_install
>> raise e
>> ProcessExecutionError: Unexpected error while running command.
>> Command: ['curtin', 'block-meta', 'custom']
>> Exit code: 3
>> Reason: -
>> Stdout: 'Creating new GPT entries.\nThe operation has completed
>> successfully.\nThe operation has completed successfully.\nAn error occured
>> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
>> file or directory\nTraceback (most recent call last):\n File
>> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
>> args.func(args)\n File "curtin/commands/block_meta.py", line 62, in
>> block_meta\nmeta_custom(args)\n File "curtin/commands/block_meta.py",
>> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
>> File "curtin/commands/block_meta.py", line 672, in format_handler\n
>> mkfs.mkfs_from_config(volume_path, info)\n File
Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices
OK; thanks. I need to work with nvme devices on Xenial; it looks like the
storage naming rules for partitions are different for NVME devices (p1, p2,
p3) versus other disks (1, 2, 3 4);
On Mon, Mar 7, 2016 at 12:54 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi Ryan,
>
> I have tried that but no luck.
>
> Config using curtin defaults:
>
> --
> cat configs/config-002.cfg
>
> partitioning_commands:
> builtin: [curtin, block-meta, custom]
> storage:
> config:
> - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
> - {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1,
> offset: 4194304B, size: 128026935296B, type: partition, uuid:
> e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
> - {fstype: ext4, id: nvme0n1-part1_format, label: 'rootfs', type:
> format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877, volume: nvme0n1-part1,
> path: /dev/nvme0n1p1}
> - {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /, type:
> mount}
> version: 1
>
> bin/curtin --showtrace --install-deps install
> --config=configs/config-002.cfg
>
> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
> Creating new GPT entries.
> The operation has completed successfully.
> The operation has completed successfully.
> An error occured handling 'nvme0n1-part1_format': ValueError -
> '/dev/nvme0n11': no such file or directory
> Traceback (most recent call last):
> File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
> File "curtin/commands/block_meta.py", line 62, in block_meta
> meta_custom(args)
> File "curtin/commands/block_meta.py", line 1083, in meta_custom
> handler(command, storage_config_dict)
> File "curtin/commands/block_meta.py", line 672, in format_handler
> mkfs.mkfs_from_config(volume_path, info)
> File "curtin/block/mkfs.py", line 207, in mkfs_from_config
> label=info.get('label'))
> File "curtin/block/mkfs.py", line 145, in mkfs
> raise ValueError("'%s': no such file or directory" % path)
> ValueError: '/dev/nvme0n11': no such file or directory
> '/dev/nvme0n11': no such file or directory
> Installation failed with exception: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nThe operation has completed successfully.\nAn error occured
> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
> file or directory\nTraceback (most recent call last):\n File
> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
> args.func(args)\n File "curtin/commands/block_meta.py", line 62, in
> block_meta\nmeta_custom(args)\n File "curtin/commands/block_meta.py",
> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
> File "curtin/commands/block_meta.py", line 672, in format_handler\n
> mkfs.mkfs_from_config(volume_path, info)\n File "curtin/block/mkfs.py",
> line 207, in mkfs_from_config\nlabel=info.get(\'label\'))\n File
> "curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
> such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such
> file or directory\n\'/dev/nvme0n11\': no such file or directory\n'
> Stderr: ''
> Traceback (most recent call last):
> File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
> File "curtin/commands/install.py", line 399, in cmd_install
> raise e
> ProcessExecutionError: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nThe operation has completed successfully.\nAn error occured
> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
> file or directory\nTraceback (most recent call last):\n File
> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
> args.func(args)\n File "curtin/commands/block_meta.py", line 62, in
> block_meta\nmeta_custom(args)\n File "curtin/commands/block_meta.py",
> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
> File "curtin/commands/block_meta.py", line 672, in format_handler\n
> mkfs.mkfs_from_config(volume_path, info)\n File "curtin/block/mkfs.py",
> line 207, in mkfs_from_config\nlabel=info.get(\'label\'))\n File
> "curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
> such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such
> file or directory\n\'/dev/nvme0n11\': no such file or directory\n'
> Stderr: ''
> Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
>
Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices
Yeah, looks like the mkfs code is expecting you to include label: 'some
label' in the format dictionary.
Can you try injecting a label into the format dictionary:
- {fstype: ext4, id: nvme0n1-part1_format, label: 'SOME_LABEL_HERE', type:
format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877,
volume: nvme0n1-part1}
This is a bug in curtin as label's aren't required.
On Sun, Mar 6, 2016 at 3:58 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> ls -la /dev/nvme0*
> crw--- 1 root root 10, 57 Mar 6 21:10 /dev/nvme0
> brw-rw 1 root disk 259, 0 Mar 6 21:44 /dev/nvme0n1
> brw-rw 1 root disk 259, 1 Mar 6 21:44 /dev/nvme0n1p1
>
> --
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> 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
>
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices
On Sat, Mar 5, 2016 at 3:56 AM, Rob Sanderson <1401...@bugs.launchpad.net> wrote: > Hi, > > I'm still seeing this issue on Xenial. > > root@maas1:~# cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=16.04 > DISTRIB_CODENAME=xenial > DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" > root@maas1:~# uname -a > Linux maas1 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016 > x86_64 x86_64 x86_64 GNU/Linux > root@maas1:~# dpkg -l|grep curtin > ii curtin-common 0.1.0~bzr359-0ubuntu1 all > Library and tools for curtin installer > ii python3-curtin 0.1.0~bzr359-0ubuntu1 all > Library and tools for curtin installer > > I have tried with the default curtin_userdata and have also tried: > > partitioning_commands: > builtin: curtin block-meta custom > > storage: > version: 1 > config: > - id: nvme0n1 > type: disk > ptable: msdos > If you don't specify a 'serial': or 'path' then curtin will attempt to deduce the path via the id. Can you try adding: path: /dev/nvme0 If that is indeed the path to the device. > - id: nvme0n1p1 > type: partition > number: 1 > size: 128GB > device: nvme0n1 > flag: boot > - id: nvme0n1p1_root > type: format > fstype: ext4 > volume: nvme0n1p1 > - id: nvme0n1p1_mount > type: mount > path: / > device: nvme0n1p1_root > > The error is as follows: > > + exec curtin --install-deps install --config=configs/config-000.cfg > --config=configs/config-001.cfg --config=configs/config-002.cfg > --config=configs/config-003.cfg --config=configs/config-004.cfg > http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz > Error: /dev/sda: unrecognised disk label > Error: /dev/sda: unrecognised disk label > Error: /dev/sdb: unrecognised disk label > Error: /dev/sdb: unrecognised disk label > Error: /dev/sdc: unrecognised disk label > Error: /dev/sdc: unrecognised disk label > An error occured handling 'nvme0n1-part1_format': ValueError - > '/dev/nvme0n11': no such file or directory > '/dev/nvme0n11': no such file or directory > Installation failed with exception: Unexpected error while running command. > Command: ['curtin', 'block-meta', 'custom'] > Exit code: 3 > Reason: - > Stdout: "Error: /dev/sda: unrecognised disk label\nError: /dev/sda: > unrecognised disk label\nError: /dev/sdb: unrecognised disk label\nError: > /dev/sdb: unrecognised disk label\nError: /dev/sdc: unrecognised disk > label\nError: /dev/sdc: unrecognised disk label\nAn error occured handling > 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': no such file or > directory\n'/dev/nvme0n11': no such file or directory\n" > Stderr: '' > Unexpected error while running command. > Command: ['curtin', 'block-meta', 'custom'] > Exit code: 3 > Reason: - > Stdout: "Error: /dev/sda: unrecognised disk label\nError: /dev/sda: > unrecognised disk label\nError: /dev/sdb: unrecognised disk label\nError: > /dev/sdb: unrecognised disk label\nError: /dev/sdc: unrecognised disk > label\nError: /dev/sdc: unrecognised disk label\nAn error occured handling > 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': no such file or > directory\n'/dev/nvme0n11': no such file or directory\n" > Stderr: '' > > -- > You received this bug notification because you are subscribed to curtin > in Ubuntu. > Matching subscriptions: curtin-bugs, curtin-bugs-all > 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 > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
