Stop action does not power systems down

Bug #1270165 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned
maas (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I had three servers connected to my MAAS server. All three were successfully enlisted, commissioned and in the "Ready" state.

I did a juju bootstrap which grabbed one server, powered it on and installed and completed Juju's bootstrap bringup. This was confirmed by running juju status.

I next wanted to confirm I could install a system directly from MAAS by simply issuing the "Start node" action. So I selected one free node and clicked the "Start node" button in the nodes details page.

This turned the node on, and it did indeed install the prescribed OS version.

Now, I wanted to release those for use elsewhere, so in the Nodes page, I selected my juju bootstrap node and my recently installed generic node (both in the "Alloctated to ubuntu" state, ubuntu is the username) and then in the Bulk Actions dropdown selected "Stop selected nodes" and clicked the Go button.

At this point, the MAAS UI refreshed and showed the systems back in the "Ready" unallocated state, indicating that I could proceed to re-enlist them. However, neither of the nodes actually powered off.

This means I will be unable to re-use those nodes without manually powering them off.

To check this, I left them in their Powered On but "Ready in MAAS" state and attempted to "Start" one wiht a different Ubuntu version chosen for it.

As predicted, the node did not reboot, reset or anything, meaning it was still running in it's previous state, regardless of what MAAS or I wanted it to do. I had to manually reset teh system to get it to come back up and PXE boot the new OS from MAAS.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.4+bzr1817+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
Uname: Linux 3.13.0-2-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 16 09:49:57 2014
InstallationDate: Installed on 2014-01-13 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140113)
PackageArchitecture: all
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jeff Lane  (bladernr) wrote :
Changed in maas:
status: New → Invalid
Changed in maas (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.