Public bug reported:
We have at least two systems in our lab that are seeing this problem. Both of
them are able to boot other images (bionic, etc) just fine, and at least one of
them was definitely booting focal earlier this week from the stream import in
maas. But now, whenever we try to provision them with the focal image, it fails
to boot for provisioning. I got someone to look at the console and take
pictures (no serial or bmc on these, sorry) and they were dropped to busybox on
boot. One error did jump out in dmesg:
/root.tmp.img: can't open blockdev
I'll also post the images of the screen for further details.
There are other devices that boot the image from maas just fine, but I
did try re-importing it just to be sure nothing was messed up with it.
The two systems we're having problems with at the moment are:
- Dell latitude 5758 i5-5200
- Dell latitude 5759 i5-6200
It's unknown yet whether there are others affected by this.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874279
Title:
failed to boot focal image in maas: /root.tmp.img: can't open blockdev
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
