If you're blocked by this issue, you can workaround it by editing /etc/maas/templates/power/ipmi.template to add use of -W opensesspriv. I've tested this on a handful of systems that don't require the workaround and it seems to work fine everywhere so far.
If you're blocked by this issue, you can workaround it by editing /etc/maas/ templates/ power/ipmi. template to add use of -W opensesspriv. I've tested this on a handful of systems that don't require the workaround and it seems to work fine everywhere so far.
=== modified file 'etc/maas/ templates/ power/ipmi. template' templates/ power/ipmi. template 2014-02-26 07:05:31 +0000 templates/ power/ipmi. template 2014-03-05 23:12:24 +0000
--- etc/maas/
+++ etc/maas/
@@ -55,9 +55,9 @@
fi
echo workaround |\ chassis_ config} ${driver_option} -h ${power_address} -u ${power_user} -p ${power_pass} --commit --filename ${config} chassis_ config} -W opensesspriv ${driver_option} -h ${power_address} -u ${power_user} -p ${power_pass} --commit --filename ${config}
- ${ipmi_
+ ${ipmi_
echo workaround |\
- ${ipmipower} ${driver_option} -h ${power_address} -u ${power_user} -p ${power_pass} "$@"
+ ${ipmipower} -W opensesspriv ${driver_option} -h ${power_address} -u ${power_user} -p ${power_pass} "$@"
}
# This script deliberately does not check the current power state