Hi Andres,
Yes that is exactly what happens. I forgot to mention that I included a
screen capture showing this in the attached bundle.

On Tuesday, July 12, 2016, Andres Rodriguez <email address hidden> wrote:

> Hi Larry,
>
> Can you confirm you see:
>
> "Unable to change power state to 'on' for node krastin: another action is
> already in progress for that node."
>
> In the UI, but the node still switches to "deploying"?
>
> On Tuesday, July 12, 2016, Larry Michel <<email address hidden>
> <javascript:;>>
> wrote:
>
> > Public bug reported:
> >
> > So, the scenario is as following. I am attempting to deploy a node. It's
> > switching to deploying but I am expecting node to be powered on and it's
> > never powered on. Looking at the event log, I see a node powered off
> > where there should have been a Powering node on/Node powered on sequence
> > events. I then retried and things went as expected.
> >
> >
> > This is different from bug 1427573 where system actually PXE'ed before
> > being Powered Off.
> >
> >
> > Event   Time
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:41:31
> > PXE Request - installation      Wed, 13 Jul. 2016 01:39:11
> > PXE Request - installation      Wed, 13 Jul. 2016 01:39:11
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:37:14
> > Node powered on Wed, 13 Jul. 2016 01:37:12
> > Powering node on        Wed, 13 Jul. 2016 01:37:07
> > User starting deployment - (larry)      Wed, 13 Jul. 2016 01:37:06
> > User acquiring node - (larry)   Wed, 13 Jul. 2016 01:37:06
> > Queried node's BMC - Power state queried: off   Wed, 13 Jul. 2016
> 01:37:01
> > User releasing node - (larry)   Wed, 13 Jul. 2016 01:36:57
> > Queried node's BMC - Power state queried: off   Wed, 13 Jul. 2016
> 01:36:04
> > Node powered off        Wed, 13 Jul. 2016 01:32:57
> > User starting deployment - (larry)      Wed, 13 Jul. 2016 01:32:47
> > User acquiring node - (larry)   Wed, 13 Jul. 2016 01:32:47
> > Queried node's BMC - Power state queried: off   Wed, 13 Jul. 2016
> 01:32:38
> > Powering node off       Wed, 13 Jul. 2016 01:32:23
> > User releasing node - (larry)   Wed, 13 Jul. 2016 01:32:23
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:31:36
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:26:02
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:20:57
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:15:43
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:10:36
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:05:12
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 01:00:13
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 00:54:58
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 00:49:42
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 00:44:27
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 00:39:12
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 00:33:57
> > Queried node's BMC - Power state queried: on    Wed, 13 Jul. 2016
> 00:29:23
> >
> > I have collected the logs and I am attaching to this bug.
> >
> > Going back to recreate, I saw this message: "Node failed to be deployed,
> > because of the following error: Unable to change power state to 'on' for
> > node krastin: another action is already in progress for that node."
> >
> > But that error message was incorrect, because node was still in the
> > Deploying state. This is something I had previously observed recently
> > where a system was in deploying state and powered off. I was able to do
> > a manual poweron and it deployed OK. But, having been able to recreate
> > it, it's looking more like an issue than a transient thing.
> >
> > The method to recreate seems to be to release the node and there's a
> > window after system switches back to the ready state where deploying
> > will fail to power on the system because it's still being powered off.
> >
> > ubuntu@maas2-integration:~$ dpkg -l '*maas*'|cat
> > Desired=Unknown/Install/Remove/Purge/Hold
> > |
> >
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> > ||/ Name                            Version
> > Architecture Description
> >
> >
> +++-===============================-==================================-============-=================================================
> > ii  maas                            2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          "Metal as a Service" is a physical cloud and IPAM
> > ii  maas-cli                        2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          MAAS client and command-line interface
> > un  maas-cluster-controller         <none>
> >  <none>       (no description available)
> > ii  maas-common                     2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          MAAS server common files
> > ii  maas-dhcp                       2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          MAAS DHCP server
> > ii  maas-dns                        2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          MAAS DNS server
> > ii  maas-proxy                      2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          MAAS Caching Proxy
> > ii  maas-rack-controller            2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          Rack Controller for MAAS
> > ii  maas-region-api                 2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          Region controller API service for MAAS
> > ii  maas-region-controller          2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          Region Controller for MAAS
> > un  maas-region-controller-min      <none>
> >  <none>       (no description available)
> > un  python-django-maas              <none>
> >  <none>       (no description available)
> > un  python-maas-client              <none>
> >  <none>       (no description available)
> > un  python-maas-provisioningserver  <none>
> >  <none>       (no description available)
> > ii  python3-django-maas             2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          MAAS server Django web framework (Python 3)
> > ii  python3-maas-client             2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          MAAS python API client (Python 3)
> > ii  python3-maas-provisioningserver 2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> > all          MAAS server provisioning libraries (Python 3)
> >
> > ** Affects: maas
> >      Importance: Undecided
> >          Status: New
> >
> >
> > ** Tags: oil
> >
> > ** Attachment added: "logs.tar.gz"
> >
> >
> https://bugs.launchpad.net/bugs/1602487/+attachment/4699809/+files/logs.tar.gz
> >
> > ** Summary changed:
> >
> > - [2.0 RC1] Node powered off soon after transitioning to deploying
> instead
> > of being Powered on
> > + [2.0 RC1] Deploying node not powered on - Unable to change power state
> > to 'on' for node krastin: another action is already in progress for that
> > node.
> >
> > --
> > You received this bug notification because you are subscribed to MAAS.
> > https://bugs.launchpad.net/bugs/1602487
> >
> > Title:
> >   [2.0 RC1] Deploying node not powered on - Unable to change power state
> >   to 'on' for node krastin: another action is already in progress for
> >   that node.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/maas/+bug/1602487/+subscriptions
> >
>
>
> --
> Andres Rodriguez (RoAkSoAx)
> Ubuntu Server Developer
> MSc. Telecom & Networking
> Systems Engineer
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1602487
>
> Title:
>   [2.0 RC1] Deploying node not powered on - Unable to change power state
>   to 'on' for node krastin: another action is already in progress for
>   that node.
>
> Status in MAAS:
>   New
>
> Bug description:
>   So, the scenario is as following. I am attempting to deploy a node.
>   It's switching to deploying but I am expecting node to be powered on
>   and it's never powered on. Looking at the event log, I see a node
>   powered off where there should have been a Powering node on/Node
>   powered on sequence events. I then retried and things went as
>   expected.
>
>
>   This is different from bug 1427573 where system actually PXE'ed before
> being Powered Off.
>
>
>   Event Time
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:41:31
>   PXE Request - installation    Wed, 13 Jul. 2016 01:39:11
>   PXE Request - installation    Wed, 13 Jul. 2016 01:39:11
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:37:14
>   Node powered on       Wed, 13 Jul. 2016 01:37:12
>   Powering node on      Wed, 13 Jul. 2016 01:37:07
>   User starting deployment - (larry)    Wed, 13 Jul. 2016 01:37:06
>   User acquiring node - (larry) Wed, 13 Jul. 2016 01:37:06
>   Queried node's BMC - Power state queried: off Wed, 13 Jul. 2016 01:37:01
>   User releasing node - (larry) Wed, 13 Jul. 2016 01:36:57
>   Queried node's BMC - Power state queried: off Wed, 13 Jul. 2016 01:36:04
>   Node powered off      Wed, 13 Jul. 2016 01:32:57
>   User starting deployment - (larry)    Wed, 13 Jul. 2016 01:32:47
>   User acquiring node - (larry) Wed, 13 Jul. 2016 01:32:47
>   Queried node's BMC - Power state queried: off Wed, 13 Jul. 2016 01:32:38
>   Powering node off     Wed, 13 Jul. 2016 01:32:23
>   User releasing node - (larry) Wed, 13 Jul. 2016 01:32:23
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:31:36
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:26:02
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:20:57
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:15:43
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:10:36
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:05:12
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 01:00:13
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 00:54:58
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 00:49:42
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 00:44:27
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 00:39:12
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 00:33:57
>   Queried node's BMC - Power state queried: on  Wed, 13 Jul. 2016 00:29:23
>
>   I have collected the logs and I am attaching to this bug.
>
>   Going back to recreate, I saw this message: "Node failed to be
>   deployed, because of the following error: Unable to change power state
>   to 'on' for node krastin: another action is already in progress for
>   that node."
>
>   But that error message was incorrect, because node was still in the
>   Deploying state. This is something I had previously observed recently
>   where a system was in deploying state and powered off. I was able to
>   do a manual poweron and it deployed OK. But, having been able to
>   recreate it, it's looking more like an issue than a transient thing.
>
>   The method to recreate seems to be to release the node and there's a
>   window after system switches back to the ready state where deploying
>   will fail to power on the system because it's still being powered off.
>
>   ubuntu@maas2-integration:~$ dpkg -l '*maas*'|cat
>   Desired=Unknown/Install/Remove/Purge/Hold
>   |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>   |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>   ||/ Name                            Version
> Architecture Description
>
> +++-===============================-==================================-============-=================================================
>   ii  maas                            2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          "Metal as a Service" is a physical cloud and IPAM
>   ii  maas-cli                        2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          MAAS client and command-line interface
>   un  maas-cluster-controller         <none>
>  <none>       (no description available)
>   ii  maas-common                     2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          MAAS server common files
>   ii  maas-dhcp                       2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          MAAS DHCP server
>   ii  maas-dns                        2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          MAAS DNS server
>   ii  maas-proxy                      2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          MAAS Caching Proxy
>   ii  maas-rack-controller            2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          Rack Controller for MAAS
>   ii  maas-region-api                 2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          Region controller API service for MAAS
>   ii  maas-region-controller          2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          Region Controller for MAAS
>   un  maas-region-controller-min      <none>
>  <none>       (no description available)
>   un  python-django-maas              <none>
>  <none>       (no description available)
>   un  python-maas-client              <none>
>  <none>       (no description available)
>   un  python-maas-provisioningserver  <none>
>  <none>       (no description available)
>   ii  python3-django-maas             2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          MAAS server Django web framework (Python 3)
>   ii  python3-maas-client             2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          MAAS python API client (Python 3)
>   ii  python3-maas-provisioningserver 2.0.0~rc1+bzr5143-0ubuntu1~xenial1
> all          MAAS server provisioning libraries (Python 3)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1602487/+subscriptions
>