[2.1rc1] AMT: If I quickly deploy and quickly release a machine, it ends up powered on
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
High
|
Unassigned |
Bug Description
I testesd this with AMT only, but this is what happend.
1. deployed machine
2. quickly selected machine to be released
I saw this in node event log:
Node powered on Tue, 12 Jul. 2016 22:07:43
PXE Request - power off Tue, 12 Jul. 2016 22:07:42
User releasing node - (admin) Tue, 12 Jul. 2016 22:07:19
Powering node on Tue, 12 Jul. 2016 22:07:15
User starting deployment - (admin) Tue, 12 Jul. 2016 22:07:14
User acquiring node - (admin) Tue, 12 Jul. 2016 22:07:14
What seems to have happened is that on the deploy action, the machine was told to power on. On the release action, the machine was not told to power off, however, since release was done quickly, the PXE request the machine made was to power off, which eventually powered off the machine.
no longer affects: | maas (Ubuntu) |
Changed in maas: | |
milestone: | 2.1.0 → 2.1.1 |
Changed in maas: | |
milestone: | 2.1.1 → 2.1.2 |
Changed in maas: | |
milestone: | 2.1.2 → 2.1.3 |
no longer affects: | maas/trunk |
no longer affects: | maas/2.0 |
Changed in maas: | |
status: | Triaged → Won't Fix |
milestone: | 2.1.3 → none |
I saw a similar issue with the virsh power driver today while testing MAAS.