Comment 0 for bug 1473167

we upgraded yesterday from:
python-maas-provisioningserver:amd64 (1.8.0~rc3+bzr4000-0ubuntu1~trusty1, 1.8.0+bzr4001-0ubuntu2~trusty1)

that potentially is the cause for this.

I have a node in maas, i deploy it via UI or cmdline and it goes into enlisting mode. the node enlists, seemingly successfully (although maas already new about it). the enlistment process changes the ipmi password, so that maas can no longer turn it on or off.

/etc/maas/maas_cluster.conf has:
MAAS_URL="http://10.245.168.2/MAAS"
CLUSTER_UUID="9a4dbe50-1015-4fe1-92ab-d37c34052733"

/var/log/maas/clusterd.log shows:
2015-07-09 17:53:17+0000 [TFTP (UDP)] Datagram received from ('10.245.168.10', 25305): <RRQDatagram(filename=/grub/grub.cfg-ec:b1:d7:75:81:a0, mode=octet, options={'blksize': '1024', 'tsize': '0'})>
2015-07-09 17:53:17+0000 [HTTPPageGetter,client] Starting TFTP back-end failed.
        Traceback (most recent call last):
        Failure: twisted.web.error.Error: 500 INTERNAL SERVER ERROR

2015-07-09 17:53:17+0000 [TFTP (UDP)] Datagram received from ('10.245.168.10', 25306): <RRQDatagram(filename=/grub/grub.cfg-default-amd64, mode=octet, options={'blksize': '1024', 'tsize': '0'})>

/var/log/maas/maas-django.log shows:

ERROR 2015-07-09 17:53:17,798 maasserver Unable to determine purpose for node: 'horsea.dellstack'
ERROR 2015-07-09 17:53:17,800 maasserver ################################ Exception: (u"Unable to determine purpose for node: '%s'", u'horsea.dellstack') ################################
ERROR 2015-07-09 17:53:17,802 maasserver Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 112, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/lib/python2.7/dist-packages/maasserver/api/pxeconfig.py", line 185, in pxeconfig
    if node is None or node.get_boot_purpose() == "commissioning":
  File "/usr/lib/python2.7/dist-packages/maasserver/models/node.py", line 1856, in get_boot_purpose
    preseed_type = get_deploying_preseed_type_for(self)
  File "/usr/lib/python2.7/dist-packages/maasserver/preseed.py", line 379, in get_deploying_preseed_type_for
    purpose = get_available_purpose_for_node(purpose_order, node)
  File "/usr/lib/python2.7/dist-packages/maasserver/preseed.py", line 348, in get_available_purpose_for_node
    "Unable to determine purpose for node: '%s'", node.fqdn)
PreseedError: (u"Unable to determine purpose for node: '%s'", u'horsea.dellstack')

regiond.log also has those errors.

2015-07-09 17:53:17 [maasserver] ERROR: Unable to determine purpose for node: 'horsea.dellstack'
2015-07-09 17:53:17 [maasserver] ERROR: ################################ Exception: (u"Unable to determine purpose for node: '%s'", u'horsea.dellstack') ################################
2015-07-09 17:53:17 [maasserver] ERROR: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 112, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/lib/python2.7/dist-packages/maasserver/api/pxeconfig.py", line 185, in pxeconfig
    if node is None or node.get_boot_purpose() == "commissioning":
  File "/usr/lib/python2.7/dist-packages/maasserver/models/node.py", line 1856, in get_boot_purpose
    preseed_type = get_deploying_preseed_type_for(self)
  File "/usr/lib/python2.7/dist-packages/maasserver/preseed.py", line 379, in get_deploying_preseed_type_for
    purpose = get_available_purpose_for_node(purpose_order, node)
  File "/usr/lib/python2.7/dist-packages/maasserver/preseed.py", line 348, in get_available_purpose_for_node
    "Unable to determine purpose for node: '%s'", node.fqdn)
PreseedError: (u"Unable to determine purpose for node: '%s'", u'horsea.dellstack')