** No longer affects: grub2 (Ubuntu Focal)
** No longer affects: grub2 (Ubuntu)
** No longer affects: linux-azure (Ubuntu Focal)
** No longer affects: linux-azure (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
** Description changed:
- A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
- 20.04 by “do-release-upgrade –d”.
+ [Impact]
+ Generic cloud images will boot without initramfs, fail, and then fall back,
resulting in a double boot performance hit
+
+ [Test Case]
+ Load up cloud
** Merge proposal linked:
https://code.launchpad.net/~patviafore/livecd-rootfs/+git/livecd-rootfs/+merge/397376
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
As an update to this bug:
The work to SRU has stalled, as we have found a regression
(https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1902260).
Once a fix is SRU'd to Groovy, I'll pick up the fix and SRU it back to
Focal.
--
You received this bug notification because you are a
Hi richmbx,
I am currently working this, and currently doing testing to make sure it
has integrated with Focal correctly. I expect it to begin the SRU
process in the next day or so.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Is there any update on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
Confirmed
Status in grub2
Hi dhbaird - sorry, the focal backport has languished in my queue for
quite a while now. I have not been able find time to focus on it.
Another developer, patviafore, has offered to take the task off my
hands, and I believe he is hoping to start looking into it at the start
of the new year. Happy
Thanks for the update @davidkrauser, and very happy that groovy is
working out. Is the fix due for focal sometime in the coming weeks or
months? Any extra info is appreciated. Also happy holidays and end of
year, and thank you all for what you do!
--
You received this bug notification because
Hi dhbaird - this was fixed in v2.672, v2.674, and v2.678 of the livecd-
rootfs package in groovy; however, those changes have not been
backported to focal, yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
Hey, is there some transparency into an actual fix here? https://cloud-
images.ubuntu.com/focal/20201210/focal-server-cloudimg-amd64.img still
has this issue. I still cannot use the cloudimg with libvirt / qemu
without modification to workaround this issue.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu
Sorry, that was v2.672 and v2.678 of the livecd-rootfs package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in
Robert Jennings's proposal from comment #33 landed in groovy v2.672.
A mechanism was also added in groovy v2.678 to detect if we've booted
using the panic fallback behavior mentioned by Steve Langasek in comment
#21.
--
You received this bug notification because you are a member of Kernel
** Changed in: cloud-images
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
** Tags added: id-5ed9564743f05c6beebe77ad
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
New
Status in
Speaking of cloud-images generally I propose the following:
* Images in the ubuntu-cpc project by default should boot with an initramfs.
* Revert the livecd-rootfs change which "Unconditionally set
GRUB_FORCE_PARTUUID in cloud images"
* Images with custom kernels can boot without an
No change is necessary on the linux-azure.
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
New
Status in grub2 package
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Won't Fix
Status
So it looks this is considered as a feature rather than a bug for the
Ubuntu 20.04 VM image in Azure Marketplacet. To whoever uses such an
image on Azure: if you're installing a new kernel that doesn't have the
necessary drivers built-in (CONFIG_HYPERV=y, CONFIG_HYPERV_STORAGE=y),
you're supposed
Awesome, thanks for categorizing that for me @vorlon! I was trying hard
to find the right home for the issue, but didn't even think of livecd-
rootfs :)
I still am not too sure about the ultimate value offered by the
initramfs fallback. It seems like you would: (a) never want initramfs,
or (b)
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Triaged
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
On Tue, May 12, 2020 at 08:51:38PM -, David Baird wrote:
> What is the cloudimg designed to boot with, if not libvirt? I think
> virtio-scsi is being used. Here's the virt-install line, if it helps,
Ok, it turns out this is a bug in the generic cloud image, which ships with
the linux-generic
On Tue, May 12, 2020 at 08:09:12PM -, Dexuan Cui wrote:
> Hi Steve, I guess you assume the pattern is
> "panic/success/success/success/...", but actually the pattern is
> “panic/success/panic/success/panic/success/...” -- this is pretty
> confusing. Please refer to the the Bug Description for
Hi! Has any information surfaced about the cloudimg kernel and virtio-
scsi?
After thinking about this for some time, I propose that the "initrdfail"
design isn't ultimately helpful and should be reverted, because: (1) It
substantially increases the complexity of grub.cfg, (2) it is not clear
BTW, the symptom described in the Bug Description also exists in the
Ubuntu 20.04 image in Azure Marketplace.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
> If someone is using a kernel other than the one we provide for the
cloud, or in the case of a bug, the system will still boot (slower)
after a panic and a reboot to try again with the initrd.
Hi Steve, I guess you assume the pattern is
"panic/success/success/success/...", but actually the
> These images should likewise be bootable under libvirt with, at most,
a boot performance penalty because of the second boot.
Well, yes, it does boot on the second boot. Not trying to be contrarian
here, but isn't a moot point that booting on the first boot is the de
facto way things should
On Tue, May 12, 2020 at 01:50:35AM -, David Baird wrote:
> Thanks for the information @vorlon. I think that makes sense.
> What would be the solution for booting focal-server-cloudimg-amd64.img
> with libvirt (virt-install) (so, not on Azure, as the OP was; so, I
> think the issue is now
Thanks for the information @vorlon. I think that makes sense.
What would be the solution for booting focal-server-cloudimg-amd64.img
with libvirt (virt-install) (so, not on Azure, as the OP was; so, I
think the issue is now fractured into two separate issues with same
underlying cause)?
Thanks.
Yes, the design here is that, since we provide custom kernels for our
cloud partners which have all the drivers needed to boot built in,
loading an initrd is a waste of time at boot.
If someone is using a kernel other than the one we provide for the
cloud, or in the case of a bug, the system will
> In my case, it's not even my system though: it's Canonical's system;
It's a fresh download of a cloudimg from https://cloud-
images.ubuntu.com/focal/ which has the issue, so it can't because I
didn't build the image right, because I didn't build the image at all.
that's correct, you didn't do
Hey Dan, thanks for getting back. In my case, it's not even my system
though: it's Canonical's system; It's a fresh download of a cloudimg
from https://cloud-images.ubuntu.com/focal/ which has the issue, so it
can't because I didn't build the image right, because I didn't build the
image at all.
You may have a file /etc/default/grub.d/40-force-partuuid.cfg in your
system, that sets the grub var GRUB_FORCE_PARTUUID. If so, you can just
comment out that line, or remove the file, and run 'sudo update-grub'.
Your /boot/grub/grub.cfg should then no longer have the initrd-less boot
with panic
I don't know how to escalate attention to this issue. Is emailing the
author of commit 6a814c759e10feafb40c3669be30aa51eb5ce39b, which seems
to have introduced the issue, acceptable? I'm surprised it's not causing
more issues. I guess people don't care about the cloud images much?
--
You
Anyone knows who maintains the grub package shipped in the cloud-images?
Should we report a bug at https://bugs.launchpad.net/ubuntu/+source/grub2 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
I think commen #6 is correct: it looks the 2018 patch introduced the
issue for us, but the patch is originally for "initrd-less boot
capabilities." and here we do need the initramfs file.
I guess the patch "ubuntu-add-initrd-less-boot-fallback.patch" is not
included into the grub shipped in the
Today I just repeated the test "Create a Gen-1 Ubuntu 19.10 VM on Azure,
and upgrade it to Ubuntu 20.04 by “do-release-upgrade –d" and I
reproduced this bug again, and the grub version is also 2.04-1ubuntu26!
So I suspect grub itself should be good, but some grub config file (i.e.
Sorry, this statement is wrong:
==
Today I also created a VM on my host from
https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-amd64-azure.vhd.zip
and can not see the bug either, and the grub version is also 2.04-1ubuntu26.
Today I installed a Generation-1 Ubuntu 20.04 VM on my local Hyper-V
host from the ISO file: https://releases.ubuntu.com/20.04/ubuntu-20.04
-live-server-amd64.iso (released on 4/23/2020) and I don't see this bug
and the grub version is 2.04-1ubuntu26.
Today I also created a VM on my host from
I'm actually not sure the best place to file a ticket for the cloudimg
distribution. Any recommendation appreciated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
Hmmm, I am not using the ISO, but rather the pre-installed cloudimg, and
I am not so sure it is actually fixed. I just tried out the latest one,
and can confirm the issue still persists with it:
https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-
amd64.img
Here is the output
When the bug was originally reported on Apr 1, "We installed a Ubuntu
20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-
live/pending/ and don’t see the strange grub issue". It looks the grub
version used in the .iso file (on Apr 1) does not have the bug.
I don't think the patch in
The git commit which introduced the issue seems to be this:
commit 6a814c759e10feafb40c3669be30aa51eb5ce39b
Author: Mathieu Trudel-Lapierre
Date: Tue Jul 16 11:31:29 2019 -0400
Import patches-unapplied version 2.04-1ubuntu1 to ubuntu/eoan-proposed
Imported using git-ubuntu
Also, this bug is not specific to just Azure. I am using libvirt and
experiencing this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get
I've traced the issue back to "00_header" and "10_linux" here:
https://git.launchpad.net/ubuntu/+source/grub2/tree/debian/patches
/ubuntu-add-initrd-less-boot-fallback.patch?h=ubuntu/focal
diffstat debian/patches/ubuntu-add-initrd-less-boot-fallback.patch
Makefile.am |3 ++
I agree with David. IMO this bug should be fixed ASAP. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package
Hi, this issue needs attention because it renders the cloud images for
Ubuntu 20.04 potentially unusable. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
This bug may also be affecting focal-server-cloudimg builds at:
https://cloud-images.ubuntu.com/focal/.
See: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1874147
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
54 matches
Mail list logo
