** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Trusty)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Tags added: hs-arm64-maas-juju
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
booting cloud image without initramfs broken
To manage notifications about this
** Attachment added: ppc64el console log without initramfs and with mountall
debug
https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4242046/+files/no-initrd-ppc64el.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Attachment added: amd64 console log without initramfs and with mountall
debug
https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4242047/+files/no-initrd-amd64.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
bah.
/etc/init/cloud-init-local.conf
- start on mounted MOUNTPOINT=/
+start on mounted MOUNTPOINT=/ and mounted MOUNTPOINT=/run
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
comment 3 above is ordered wrong. the change that caused this is:
/etc/init/cloud-init-local.conf
+start on mounted MOUNTPOINT=/
+start on mounted MOUNTPOINT=/ and mounted MOUNTPOINT=/run
the reason was that cloud-init-local needs to write to / and to /run.
previously it was using /run without
ok. so i can reproduce this on both arm64 and ppc64el.
On ppc64el, both on trusty and on utopic.
Adding '-initrd extracted-initramfs' fixes the problem.
Heres an improved copy/paste to recreate. It does *not* fail on
(arch=amd64).
arch=ppc64el
rel=trusty
** Attachment added: amd64 console log
https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4241189/+files/log-amd64.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Attachment added: ppc64el console log
https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4241190/+files/log-ppc64.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
a bit more info. on ppc64el at least, you can boot with 'rw' as a kernel
parameter and fix this. thats less than ideal, but it adds an
interesting piece of information. previously i just assumed we were
blocked in a hang where / was mounted rw but /run was not yet mounted.
it is the other way,
** Tags added: hs-moonshot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
booting cloud image without initramfs broken
To manage notifications about this bug go
** Tags removed: hs-moonshot
** Tags added: hs-moonshot-maas-juju
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
booting cloud image without initramfs broken
To
** Tags added: hs-arm64
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
booting cloud image without initramfs broken
To manage notifications about this bug go to:
so to clarify above, i could not recreate the error on amd64, but it
most certainly *does* fail on arm64 (AArch64).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
The offensive change was this in /etc/init/cloud-init-local.conf
-start on mounted MOUNTPOINT=/ and mounted MOUNTPOINT=/run
+start on mounted MOUNTPOINT=/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Attachment added: ubuntu.console: old ubuntu (good) boot log
https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4223940/+files/ubuntu-old.console
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Attachment added: ubuntu-patched.console: current ubuntu patched with sed
https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4223941/+files/ubuntu-patched.console
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Attachment added: ubuntu.console: current ubuntu (failing) boot log
https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4223939/+files/ubuntu.console
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in
** Attachment added: ubuntu-with-ramdisk.console: current ubuntu with ramdisk
https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4223942/+files/ubuntu-with-ramdisk.console
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Description changed:
Booting without a initramfs was broken by the cloud-init change for
- bug 1377005 (http://pad.lv/1377005).
+ bug 1353008 (http://pad.lv/1353008).
This affects arm guests where a bootloader is not used that would load
kernel and initramfs.
There are 2
I just noticed from reading one of the related bugs that booting image
without 'ro' on the kernel command line might also be a requirement to
trigger this. I'd like to see a kernel booted iwth 'ro' on the command
line .
that said, I tried to reproduce this with a daily image of trusty
21 matches
Mail list logo
