This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs
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-p
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/cur
Hi Ryan,
I'm more than happy to let maas supply the data, I'm only trying to
override the default behaviour by adding to
/etc/maas/preseeds/curtin_userdata to get around the nvme bug.
Here's the output:
root@maas1:~# maas admin node get-curtin-config
node-4c4aecf2-e332-11e5-a740-00163e1ca9db
Su
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
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 con
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: s
Also worth noting that curtin runs:
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-
OK, just recommissioning the node so I can retest. 20 mins!
--
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 noti
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
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
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 tri
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: n
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,
vo
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 a member of Ubuntu
Bugs, which is subscribed to Ubunt
Hi, thanks for the reply.
Specifying the path doesn't appear to help. I have tried the following:
* Commissioned a new server
* Set disk config in web ui:
Used disks and partitions
Name Model Serial BootDevice typeUsed for
nvme0n1PhysicalGPT partitioned with 1 partition
nvme0
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 br
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 20
This bug was fixed in the package curtin - 0.1.0~bzr221-0ubuntu1~14.10.1
---
curtin (0.1.0~bzr221-0ubuntu1~14.10.1) vivid-proposed; urgency=medium
* New upstream snapshot.
- support installation to multipath devices. (LP: #1371634)
- know that kernel version 4.2.0 maps to li
This bug was fixed in the package curtin - 0.1.0~bzr221-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr221-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- support installation to multipath devices. (LP: #1371634)
- know that kernel version 4.2.0 maps to l
We've successfully deployed using latest curtin to the systems that were
causing problems (primarily nvme systems and ccis systems).
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Description changed:
== Begin SRU Template ==
[Description]
Installing to a system with a NVM Express card/block device will fail,
showing something to the effect of:
- Could not stat /dev/nvme0n11 --- No such file or directory
+ Could not stat /dev/nvme0n11 --- No such file or direc
** Branch linked: lp:ubuntu/vivid-proposed/curtin
--
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
Hello Tycho, or anyone else affected,
Accepted curtin into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr221-0ubuntu1~14.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. Se
** Branch linked: lp:ubuntu/trusty-proposed/curtin
--
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
Hello Tycho, or anyone else affected,
Accepted curtin into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr221-0ubuntu1~14.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. S
** Description changed:
+ == Begin SRU Template ==
+ [Description]
+ Installing to a system with a NVM Express card/block device will fail,
showing something to the effect of:
+ Could not stat /dev/nvme0n11 --- No such file or directory
+
+ This is due to curtin's fairly innocent understanding
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/trusty-sru
--
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 not
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Fix Released
** Changed in: curtin
Status: New => Fix Committed
** Also affects: curtin (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also aff
29 matches
Mail list logo
