Marking this bug 'New' for the kernel, since this has to do with the
Intel NVMe device links, not the related SMP issue that came up.
** Changed in: maas
Status: Invalid => Won't Fix
** Summary changed:
- [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
+ Intel NVMe driver does
After further troubleshooting with cgregan, we've further narrowed this
down.
We ran the following script on the node that was having trouble:
https://gist.github.com/pontillo/0b92a7da2fba43fb5dce705be2dcf38b
Unlike all the other devices MAAS works with, the Intel NVMe device
reports a serial
I discussed this with cgregan on IRC and I think we came to the
conclusion that the MAAS/curtin bug is simply that the two kernels
(commissioning vs. ephemeral deployment) gather different (or missing)
unique identifiers for each drive.
To validate that, I would run the following on each kernel
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
[2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
Dan,
Bug above, but since you say it is only happening to me, have other tests been
run using MAAS 2.1.2?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
[2.1.1] MAAS has nvme0n1 set
Additional bug opened: https://bugs.launchpad.net/maas/+bug/1653797
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
[2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
To manage
> What should be the focus of the new bug?
I don't know why it doesn't work on your system, as it does work on
mine, so I can't tell you what to put in the new bug. Since your system
is smp with 2 or more cpus, it doesn't appear to be the same as this bug
(since this bug was taken over after you
Dan,
What should be the focus of the new bug? Split off the fact that Denial
cannot be deployed by MAAS? Or is it still related to nvme, just
differently?
On Dec 23, 2016 19:05, "Dan Streetman" <
dan.streetman+launch...@canonical.com> wrote:
> Chris, as your specific problem seems different than
I built a test kernel with this fix applied to the 4.4.0-57 kernel, available
here:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1651602
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Chris, as your specific problem seems different than the 1-cpu NVMe bug
that the rest of this bug describes, and my patch fixes, can you open a
new bug please.
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I tested on my nvme system with the boot param 'maxcpus=0' (i.e. UP mode), the
boot fails with kernel 4.4.0-57, because the nvme drive fails enumeration, with
the error from comment 2. With the 4.4.0-57 kernel including my nvme patch,
and using boot param 'maxcpus=0', the boot succeeds. The
** Attachment added: "syslog_kern.tar.gz"
https://bugs.launchpad.net/maas/+bug/1651602/+attachment/4795854/+files/syslog_kern.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
[2.1.1] MAAS has nvme0n1 set as boot disk,
** Attachment added: "curtin_config.tar.gz"
https://bugs.launchpad.net/maas/+bug/1651602/+attachment/4795743/+files/curtin_config.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Dan Streetman suggested that this should only be a problem with a single cpu
system.
I did verify that the failure shown above goes away if you add '-smp cpus=2' to
the qemu command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Recreate is as show above, or:
qemu-system-x86_64 -enable-kvm \
-drive file=disk1.qcow,if=none,format=qcow2,id=nvme0 \
-device nvme,drive=nvme0,serial=nvme-0 \
-snapshot -nographic -echr 0x05 -m 512 \
-kernel kernel -initrd initrd \
-append "root=LABEL=cloudimg-rootfs
Seems only present in xenial, 4.4.0-57-generic.
** Changed in: linux (Ubuntu Xenial)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
[2.1.1] MAAS has
I've just now tested yakkety, and it seems like both 4.8.0-30-generic
and 4.8.0-32-generic are working fine, so I do not believe this to
affect yakkety.
** No longer affects: linux (Ubuntu Yakkety)
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug
Just to be clear, the failure I'm seeing is that in qemu, if you try to
boot with root=LABEL=cloudimg-rootfs it will no longer work.
I believe that this is another symptom of both the failure in vmtest and
the failure that Chris saw.
The reproduce above is just easier to run.
--
You received
OK, so I installed vmlinuz-4.4.0-57-generic into the good image (apt-get
install linux-virtual) and the resulted kernel/initrd still show the
problem.
So this is squarely a kernel regression.
** Summary changed:
- [2.1.1] Yakkety - MAAS has nvme0n1 set as boot disk, curtin fails
+ [2.1.1] MAAS
20 matches
Mail list logo
