crm_* commands output should be (null) escaped in OCF scripts
Bug Description
With Corosync 2 and Pacemaker 1.1.12, crm_node, crm_attribute and other commands may return (null) strings sometimes. Exact circumstances are unknown.
Example:
crm_node --list
2 (null)
1 node-1.
3 (null)
But OCF scripts are expecting instead:
crm_node --list
1 node-1.
A workaround is to escape (null) strings with sed -e '/(null)/d'. A complete solution is unknown as well as a root cause.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit d49c1e3031bbbf1
Author: Bogdan Dobrelya <email address hidden>
Date: Tue Jan 27 13:43:51 2015 +0100
Escape null strings from crm_* commands output
W/o this patch, when Pacemaker v1.1.12, OCF scripts
could parse crm_node, crm_attribute commands output
in a wrong way as it may contain "(null)" strings.
The workaround is to escape these null strings with
a sed command.
Closes-bug: #1415021
Change-Id: Ia7670a4f1b8540
Signed-off-by: Bogdan Dobrelya <email address hidden>
Verified on ISO #92
"build_id": "2015-02-
Fix proposed to branch: master
/review. openstack. org/150395
Review: https:/