Hide Forgot
# pcs node unstandby virt-171 Actual results: > Error: error running crm_mon, is pacemaker running? (???) Expected results: > Error: cluster stack does not appear running > Solution: issue "pcs cluster start virt-171" if you want > to bring it up (in that case, the node will come online > in standby mode) Ditto at least "node unmaintenance".
As discussed, I don't see this request as unjustified. Pcs user should not face cryptic messages referring to "crm_mon" (why she would need to bother investigating what that stands for?) and what I proposed is the ideal pcs should be gradually approaching. As a first step in such a journey would be for pcs to stop being cryptic (an in turn, hostile to the users), perhaps suggesting "pcs cluster start" when suitable, per original suggestion. In order to keep track on that, I am reopening the bug, with a slightly shifted objective.
[vm-rhel72-1 ~] $ pcs status | grep Online Online: [ vm-rhel72-1 vm-rhel72-3 ] [vm-rhel72-1 ~] $ pcs node standby vm-rhel72-3 [vm-rhel72-1 ~] $ service pacemaker stop Redirecting to /bin/systemctl stop pacemaker.service [vm-rhel72-1 ~] $ pcs node unstandby vm-rhel72-3 Error: error running crm_mon, is pacemaker running? [vm-rhel72-1 ~] $ pcs cluster start vm-rhel72-3 vm-rhel72-3: Starting Cluster... [vm-rhel72-1 ~] $ pcs node unstandby vm-rhel72-3 Error: error running crm_mon, is pacemaker running? I think "pcs cluster start" is not always the solution for this situation.
(as an aside particularly for standby state, there will likely be another modifier of how the pacemaker will come up, via PCMK_node_start_state var: https://github.com/ClusterLabs/pacemaker/pull/1141)
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.