Comment 14 for bug 1950792

Still a problem on _random_ supermicro hardware: i have 15 identical nodes(AS -1123US-TR4 on H11DSU-iN motherboards), set kernel parameters for `console=ttyS0 console=tty0` and now _one_ node will not commission or therefore provision with this error. Maas (snap) at 3.2.7-12037-g.c688dd446 or 3.3.2-13177-g.a73a6e2bd

On a related note: the maas UI doesn't update the parameters passed when saved, user has to refresh the page or it keeps showing up as the last set of parameters at page-load.

After setting the parameters back to blank, this one node still cannot boot from MAAS - whatever broke, broke persistently.

Changing which image is sent (focal or jammy) does nothing, same with selecting various kernels. Once a user touches the kernel command line parameters, even if they subsequently remove them, it will break at least some nodes' ability to boot - this seems like a high severity bug which has been open for 2y.

My case is occurring in pure UEFI mode (legacy boot disabled), after a failed deployment of Ceph via Juju already installed Ubuntu on the machine. Prior to the installation of Ubuntu, the host did boot correctly with kernel parameters set.

Running `maas admin maas get-config name=kernel_opts value=" console=ttyS0 console=tty0 "`, installing an OS, and then trying to boot the node from PXE via maas again causes the breakage. Subsequently clearing `kernel_opts` to read as
```
$ maas admin maas get-config name=kernel_opts
Success.
Machine-readable output follows:
""
```
does not fix whatever the initial setting broke. Looks like there is a side-effect that cannot be undone.