Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJan Pokorný [poki]
2016-09-12 19:07:35 UTC
# 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".
Comment 3Jan Pokorný [poki]
2016-09-13 14:15:22 UTC
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.
Comment 5Jan Pokorný [poki]
2016-09-13 15:13:25 UTC
(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)
Comment 8RHEL Program Management
2020-12-15 07:45:44 UTC
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.