[Bug 1488594] Re: Nodes cannot boot after a storage disk replacement

[Blake Rouse]

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-session block-device update 1 model= serial= size=
block_size=

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to syslinux in Ubuntu.
https://bugs.launchpad.net/bugs/1488594

Title:
  Nodes cannot boot after a storage disk replacement

Status in MAAS:
  Invalid
Status in syslinux package in Ubuntu:
  New

Bug description:
  I'm experiencing this issue when I replace any osd disk on any ceph
  storage node and then reboot it. Immediatly after the node pxe boots,
  the node will hang at a "booting local disk" message and fails to
  timeout or boot. A work-around I've found to get a node to boot after
  a storage disk replacement is to momentarilly disable maas from
  managing the network after the power on of a node who's disk has been
  replaced; following that, after the node pxe boot times out and it
  results to booting from local disk into the os, I re-enable maas
  management on that network so the node gets an ip and continues the
  boot process and eventually successfully boots.

  It would be nice to get some feedback on what is going on here, and
  also a best practice for what/how to proceed in the case when you need
  to swap storage disks.

  Thanks!

  maas.log <-- http://paste.ubuntu.com/12193844/

  clusterd.log <-- http://paste.ubuntu.com/12193842/

  maas - 1.8.0+bzr4001-0ubuntu2~trusty1
  trusty - 14.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1488594/+subscriptions