[Bug 1401190] Re: curtin makes assumptions about partition names on all devices

Rob Sanderson 1401190 at bugs.launchpad.net
Mon Mar 7 19:50:55 UTC 2016


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 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.

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?

Cheers,
Rob

-- 
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



More information about the Ubuntu-server-bugs mailing list