Fix: Fencing: Correctly record which peer performed the fencing operation
Fix: crmd: Do not erase the status section for unfenced nodes
Fix: crmd: Actions can only be executed if their pre-requisits completed successfully
Log: crmd: device isn't hooked up yet, don't bother logging it
Fix: PE: Ensure unfencing only happens once, even if the transition is interrupted
Fix: PE: Do not unfence nodes that are offline, unclean or shutting down
Fix: xml: Resolve memory leak when logging xml blobs
Test: fence_dummy does not support the list command
Fix: PE: Log when resources require fencing but fencing is disabled
Merge pull request #497 from inouekazu/fix_condition

Fix: PE: Log when resources require fencing but fencing is disabled
High: pengine: Allow container nodes to migrate with connection resource
Fix: pengine: handles edge case where container order constraints are not honored during migration
Low: pengine: regression tests for remote-allow-migrate
Fix: PE: Unfencing is based on device probes, there is no need to unfence when normal resources are found active
Merge pull request #489 from davidvossel/container-node-migrate

support container remote-node migration
Test: PE: Unfencing is based on device probes, there is no need to unfence when normal resources are found active
Fix: crm_node: Only remove the named resource from the cib