MAAS tries to power query node with ether_wake power type

General Problem Description:

I have a lot of old Lenovo ThinkCenter Desktops which I want to use in a Opensstack-Coud

Powering on a node on the commandline works fine if I do it with this:
root@os1:~# etherwake 00:1e:37:45:1c:16

Using "wakeonlan" doesn't work - so I uninstalled it as I saw that it't not needed in /etc/maas/templates/power/ether_wake.template

But MAAS is failing to power it on. I can't find any hint why. Thats the only message I get:

Nov 26 10:06:31 os1 maas.power: [ERROR] impeccable-beam.maas: Failed to query power state: Unknown power_type 'ether_wake'.

1. The error log " /var/log/maas/maas.log" is full of entries like this:

Nov 26 11:42:50 os1 maas.node: [INFO] private-help.maas: Commissioning started
Nov 26 11:43:31 os1 maas.lease_upload_service: [INFO] Uploading 1 DHCP leases to region controller.
Nov 26 11:45:40 os1 maas.node: [INFO] private-help.maas: Stopping monitor: node-f5742194-7557-11e4-9333-00055d80d51c
Nov 26 11:46:02 os1 maas.node: [INFO] private-help.maas allocated to user georg
Nov 26 11:46:02 os1 maas.node: [INFO] private-help.maas: Starting monitor: {u'deadline': datetime.datetime(2014, 11, 26, 11, 26, 2, 592452, tzinfo=<twisted.protocols.amp._FixedOffsetTZInfo object at 0x7f01e77b26d0>), u'id': u'node-f5742194-7557-11e4-9333-00055d80d51c', u'context': {u'node_status': 9, u'timeout': 2400.0}}
Nov 26 11:46:02 os1 maas.dns: [INFO] Generating new DNS zone file for maas
Nov 26 11:46:02 os1 maas.calls: [INFO] Starting task 'write_dns_zone_config' with args: () {'zones': [<provisioningserver.dns.zoneconfig.DNSForwardZoneConfig object at 0x7f01c1c18f10>], 'callback': provisioningserver.tasks.rndc_command([u'reload', u'maas'])}
Nov 26 11:46:02 os1 maas.calls: [INFO] Starting task 'rndc_command' with args: ([u'reload', u'maas'],) {}
Nov 26 11:46:02 os1 maas.calls: [INFO] Finished task 'rndc_command' with args: ([u'reload', u'maas'],) {}
Nov 26 11:46:02 os1 maas.calls: [INFO] Finished task 'write_dns_zone_config' with args: () {'zones': [<provisioningserver.dns.zoneconfig.DNSForwardZoneConfig object at 0x7f01c1c18f10>], 'callback': provisioningserver.tasks.rndc_command([u'reload', u'maas'])}
Nov 26 11:46:02 os1 maas.dns: [INFO] Generating new DNS zone file for 6.168.192.in-addr.arpa
Nov 26 11:46:02 os1 maas.calls: [INFO] Starting task 'write_dns_zone_config' with args: () {'zones': [<provisioningserver.dns.zoneconfig.DNSReverseZoneConfig object at 0x7f01c0b82e50>], 'callback': provisioningserver.tasks.rndc_command([u'reload', u'6.168.192.in-addr.arpa'])}
Nov 26 11:46:02 os1 maas.calls: [INFO] Starting task 'rndc_command' with args: ([u'reload', u'6.168.192.in-addr.arpa'],) {}
Nov 26 11:46:02 os1 maas.calls: [INFO] Finished task 'rndc_command' with args: ([u'reload', u'6.168.192.in-addr.arpa'],) {}
Nov 26 11:46:02 os1 maas.calls: [INFO] Finished task 'write_dns_zone_config' with args: () {'zones': [<provisioningserver.dns.zoneconfig.DNSReverseZoneConfig object at 0x7f01c0b82e50>], 'callback': provisioningserver.tasks.rndc_command([u'reload', u'6.168.192.in-addr.arpa'])}
Nov 26 11:46:02 os1 maas.power: [INFO] Changing power state (on) of node: private-help.maas (node-f5742194-7557-11e4-9333-00055d80d51c)
Nov 26 11:46:31 os1 maas.power: [ERROR] private-help.maas: Failed to query power state: Unknown power_type 'ether_wake'.
Nov 26 11:46:31 os1 maas.lease_upload_service: [INFO] Uploading 2 DHCP leases to region controller.

2.

ii maas 1.7.0+bzr3299-0ubuntu1~trusty all MAAS server all-in-one metapackage
ii maas-cli 1.7.0+bzr3299-0ubuntu1~trusty all MAAS command line API tool
ii maas-cluster-controller 1.7.0+bzr3299-0ubuntu1~trusty all MAAS server cluster controller
ii maas-common 1.7.0+bzr3299-0ubuntu1~trusty all MAAS server common files
ii maas-dhcp 1.7.0+bzr3299-0ubuntu1~trusty all MAAS DHCP server
ii maas-dns 1.7.0+bzr3299-0ubuntu1~trusty all MAAS DNS server
ii maas-proxy 1.7.0+bzr3299-0ubuntu1~trusty all MAAS Caching Proxy
ii maas-region-controller 1.7.0+bzr3299-0ubuntu1~trusty all MAAS server complete region controller
ii maas-region-controller-min 1.7.0+bzr3299-0ubuntu1~trusty all MAAS Server minimum region controller
ii python-django-maas 1.7.0+bzr3299-0ubuntu1~trusty all MAAS server Django web framework
ii python-maas-client 1.7.0+bzr3299-0ubuntu1~trusty all MAAS python API client
ii python-maas-provisioningserver 1.7.0+bzr3299-0ubuntu1~trusty all MAAS server provisioning libraries

3. I configured two NICs:

* 192.168.6.2 (managed DNS and DHCP) - thats where all nodes connect
* 192.168.0.2 (unmanaged)

I can add nodes as long as I power them on by hand.
Aquiring works to but if I want to start the node by pressing the start button - then nothing happens.
If I run etherwake by hand it works. I would like to know whick command is actually run by maas in the background in ordter to power on the nods with wake-on-lan packets?