power parameters for probe-and-enlist mscm no longer saved for enlisted nodes

[Newell Jensen]

This used to work and no longer does. I suspect it may have to do with the celery-to-rpc conversion that has been taking place.

This command:

ubuntu@c11n1-avaton:~$ maas slayton node-group probe-and-enlist-mscm 5c54c7b2-114d-41f1-8507-f1887f7b3dc5 host=10.228.64.210 username=Administrator password=password

Only gave this log output (/var/log/maas/*.log):

http://paste.ubuntu.com/8374149/

This stood out to me the most:

==> /var/log/maas/maas-django.log <==
ERROR 2014-09-18 00:10:03,665 twisted {}

[Raghuram Kota (rkota)]

This bug is currently blocking MaaS enablement on TI-Slayton on Hp Moonshot platform, which is on a tight schedule to complete server certification by Oct 3rd, 2014 . Once fixed, The fix will need to be backported & SRUed to Trusty in time to for a sucecssful certification run on that date

Request prompt action to help resolve this bug.

Thanks,
Raghu

[Julian Edwards (julian-edwards)]

Raghuram, I don't understand how it can be blocking anything, this problem only exists in trunk, and no released version. If you are having a problem with trusty, it's a different problem.

[Andrew Cloke (andrew-cloke)]

Hi Julian, the MAAS enablement for Slayton is only in trunk right now. This bug is blocking the SRU'ing of the MAAS trunk changes into Trusty. Slayton certification must take place from Trusty. Hence the dependency, and urgency.

[Graham Binns (gmb)]

There's a definite bug in node creation whereby power parameters don't get saved. Working on fixing it now.