Comment 10 for bug 1340172

Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.

Unfortunately this bug is old for us to consider having an sysv-compatible
option to put the cluster into maintenance mode. Corosync is also being managed,
for sometime now, by systemd so this particular change wouldn't make much sense.
IMHO this type of cluster change should be done by the cluster administrator in
specific tools like crmsh, pcs, and not in an init script.

It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.