It looks like commissioning is not timing out if PXE boot fails.
We have 2 systems that are stuck in commissioning, one of them is in that state since last week and another have been in that state for past hours. Commissioning hasn't timed out for both.
phanpy:
Queried node's BMC - Power state queried: on Wed, 12 Apr. 2017 18:42:30
Node powered on Wed, 12 Apr. 2017 07:56:31
Powering node on Wed, 12 Apr. 2017 07:56:25
User starting node commissioning - (ltrager) Wed, 12 Apr. 2017 07:56:23
Node powered off Wed, 12 Apr. 2017 07:56:14
Queried node's BMC - Power state queried: off Wed, 12 Apr. 2017 07:56:13
Powering node off Wed, 12 Apr. 2017 07:56:09
User aborting node commissioning - (ltrager) Wed, 12 Apr. 2017 07:56:09
Node powered on Wed, 12 Apr. 2017 07:01:25
Powering node on Wed, 12 Apr. 2017 07:01:20
drilbur:
Queried node's BMC - Power state queried: on Wed, 12 Apr. 2017 18:43:12
Queried node's BMC - Power state queried: on Mon, 10 Apr. 2017 20:19:43
Node powered on Thu, 06 Apr. 2017 02:35:06
Powering node on Thu, 06 Apr. 2017 02:35:01
User starting node commissioning - (larry) Thu, 06 Apr. 2017 02:35:01
Node powered off Thu, 06 Apr. 2017 02:34:57
Queried node's BMC - Power state queried: off Thu, 06 Apr. 2017 02:34:57
ubuntu@maas2-production-22rc1:~$ 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.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 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.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.2.0~beta5+bzr5922-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)
This may already be fixed in 2.2rc2, but just keeping it open as I came across it myself.