[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for MAAS because there has been no activity for 60 days.]
** Changed in: maas
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950792
Title:
We suspect that on the affected systems the length of the kernel options
cmdline exceeds the allowed maximum. Would it be possible to share the
kernel options MAAS sends for machines that fail to deploy this way? The
kernel options could be retrieved using IPMI console.
** Changed in: maas
I also encountered something similar, some computes randomly are unable to boot
I may check disabling this HTTP boot
$ maas root maas get-config name=kernel_opts
Success.
Machine-readable output follows:
"console=tty0 console=ttyS0,115200n8"
** Attachment added: "Screenshot from 2023-07-26
Figured out what made that one node different from the rest: its UEFI network
boot stack had both PXE and HTTP enabled, while the others were PXE only.
After i added the kernel boot parameters, MAAS started to truncate the HTTP URI
by a few characters (and now keeps doing that even if the kernel
Still a problem on _random_ supermicro hardware: i have 15 identical
nodes, set kernel parameters for `console=ttyS0 console=tty0` and now
_one_ node will not commission or therefore provision with this error.
Maas (snap) is at 3.2.7-12037-g.c688dd446
The maas UI doesn't update the parameters
Happy to provide more info/logs/whatever if you can tell me where to
look ;-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950792
Title:
No boot possible - Cannot open root device
I am having similar problems since updating from 3.0 to the latest
release 3.2.6
We mainly use legacy boot (instead of UEFI) and the boot order of all our nodes
is set to:
1. Network/PXE
2. harddisk
A deployed node would boot PXE and then immediately MAAS tells it (not
sure how exactly) to boot
>From what I see, this could be indeed an issue with missing driver for
the specific network card in the initrd.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: Incomplete => Triaged
** Changed in: maas
Importance: Undecided =>
9 matches
Mail list logo
