[2.5] Machines are being rebooted after commissioning during enlistment happens.

Bug #1786561 reported by Andres Rodriguez on 2018-08-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Lee Trager

Bug Description

In the CI I've noticed that machines are being rebooted after enlistment + commissioning happens. I'm not yet quite sure whether this is because power management is powering them on (which doesn't seem to be the case) but rather, this would seem as if the ephemeral environment is telling them to reboot after commissioning during enlistment finishes.

Changed in maas:
importance: Undecided → High
milestone: none → 2.5.0alpha2
tags: added: track
Changed in maas:
status: New → Triaged
Changed in maas:
assignee: nobody → Lee Trager (ltrager)
Lee Trager (ltrager) on 2018-08-13
Changed in maas:
status: Triaged → In Progress
Lee Trager (ltrager) wrote :

I think this is a problem with the system firmware, not MAAS. The enlistment environment is hard coded to shutdown when done(see src/maasserver/compose_preseed.py:compose_enlistment_preseed). I entered the IPMI console and found that all of the booted machines were stuck in firmware, no OS was loaded. One had the following error message:

Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.06) - Operation
 - 1719-Slot 0 Drive Array - A controller failure event occurred prior
   to this power-up. (Previous lock up code = 0x13) Action: Install the
   latest controller firmware. If the problem persists, replace the

Changed in maas:
status: In Progress → Incomplete
Changed in maas:
milestone: 2.5.0alpha2 → 2.5.0beta1
Changed in maas:
milestone: 2.5.0beta1 → 2.5.0beta2
Changed in maas:
status: Incomplete → Invalid
milestone: 2.5.0beta2 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers