[Bug 1532935] Re: Nodes stuck at grub menu when attempting to deploy

John George john.george at canonical.com
Thu May 26 15:40:18 UTC 2016

Typing 'normal' at the prompt does boot the system.

So far a trusty kernel has been used during install. I'll see if there
is a hwe-xenial kernel available through MaaS, although this issue is
intermittent, so all I could do is run with it for awhile and see if the
issue reproduces.

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.

  Nodes stuck at grub menu when attempting to deploy

Status in curtin:
Status in grub:
Status in MAAS:
Status in maas-images:
Status in grub2 package in Ubuntu:

Bug description:
  Build Version/Date: Current revision: 9592
  MAAS Version 1.9.1+bzr4543-0ubuntu1 (trusty1)
  Juju-core 1.25.3-0ubuntu1~15.10.1~juju1

  Environment used for testing:

  When autopilot attempts to deploy Openstack, 1-2 nodes fail to deploy. Investigation reveals that they are booting into a grub menu. It seems the MAAS directed boot is not completed properly. This failure seems to only happen when Autopilot is deploying the nodes. When deploying nodes using MAAS directly, this issue is not re-producible.

  Steps to Reproduce:
  1) Provide Landscape with credentials to MAAS with 8 physical nodes
  2) Select Ceph/Swift configuration
  3) Deploy and monitor MAAS node status

  Expected result:
  Nodes deploy to fully working HA Openstack

  Actual result:
  A couple nodes fail to deploy and are stuck at a grub menu.

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list