** Changed in: maas
Milestone: next => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488594
Title:
Nodes cannot boot after a storage disk replacement
To manage notifications about this bu
If you know which is the old disk and you have the fully information for
the new disk using the API you could update that disk with all the new
disk information. You would need to be very sure about the data or the
deployment would fail, that is why its recommended to re-commission.
maas my-maas-s
I really appreciate the input everyone. I guess I was a little overwhelmed
dealing with a few different issues at once I didn't mean to place the
blame on MAAS. That being said, node disk replacement under the direction
of MAAS is still a rugged process for me. I understand that pxelinux/bios
I really appreciate the input everyone. I guess I was a little
overwhelmed dealing with a few different issues at once I didn't
mean to place the blame on MAAS. That being said, node disk replacement
under the direction of MAAS is still a rugged process for me. I
understand that pxelinux/bios
Even when a node has been deployed, the node still attempts to PXE boot
from MAAS each time it's rebooted. MAAS knows it should boot locally and
gives the following configuration to PXELINUX:
DEFAULT local
LABEL local
LOCALBOOT 0
It appears that this does not do the right thing for your
