The recent changes to power handling broke a key feature - the ability to add arbitrary
arguments to the generated fence command. Templates such as ipmilan document using the
power_id field for things like adding "-P -T 4" for HP iLO3 power manipulation,
port info for some fence types, etc.
In Cobbler 2.0, anything in the power_id field was simply inserted as-is into the command
line. This was flexible and worked beautifully in our environment.
In Cobbler 2.2.3, however, instead of using command line parameters everything is mapped
to stdin lines passed to the subprocess. Unfortunately that results in power_id being
treated as a single parameter, passed as "\nport=-P -T4", which is rejected
since port isn't a valid input for fence_ipmilan; to be equivalent it should have
passed "\nlanplus\npower_wait=4" instead.
SOME ability to provide arbitrary per-machine settings to be passed to the fence command
needs to be restored. This could be via command line arguments, a la Cobbler 2.0, via
optional stdin lines, a la the translation Cobbler 2.2.3 does, a mixture of both,
whatever.
Regards,
Doug
----
MC Linux Infrastructure, 970-898-4860, Fort Collins 3UR8 (MS 57)
"The best way to cope with change is to help create it."