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.
Bug 1032161 - pcs cluster standby nodename doesn't work
Summary: pcs cluster standby nodename doesn't work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact:
URL:
Whiteboard:
Depends On: 1029129
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-19 16:03 UTC by Jan Kurik
Modified: 2018-12-03 20:44 UTC (History)
14 users (show)

Fixed In Version: pcs-0.9.90-2.el6_5.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-17 10:10:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 545793 0 None None None Never
Red Hat Product Errata RHBA-2013:1848 0 normal SHIPPED_LIVE pcs bug fix update 2013-12-17 15:09:19 UTC

Description Jan Kurik 2013-11-19 16:03:30 UTC 
This bug has been copied from bug #1029129 and has been proposed
to be backported to 6.5 z-stream (EUS).
Comment 4 RHEL Program Management 2013-11-27 22:26:20 UTC 
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Comment 5 xrobau 2013-11-28 02:09:29 UTC 
I'd like to appeal this, please.

This is _critical functionality_ of Clustering - the ability to set a node to standby status.

Whilst there are workarounds for this specific issue, there are numerous other high priority bugs that are caused by this.

Whilst I didn't outline them all, there are at least 10 other cluster-breaking bugs in PCS caused by this.

https://bugzilla.redhat.com/show_bug.cgi?id=1029129#c9

(I realise that Fabio Di Nitto has already reopened this, and if this was closed in error, then I apologise, but I thought I better make sure everyone's aware that this is a critical level issue)
Comment 6 Chris Feist 2013-12-02 23:59:31 UTC 
This was closed in error (and has been re-opened).

I've also look at the https://bugzilla.redhat.com/show_bug.cgi?id=1029129#c9, I don't believe there are 10 other cluster-breaking bugs.  The majority of the times that function is called it is called in commands that are not supported in RHEL 6.5 (generally commands that require pcsd or commands that operate on remote nodes).

The only two bugs that have come out of that issue are this bug & https://bugzilla.redhat.com/show_bug.cgi?id=1019410 (cluster standby and fence/stonith levels).  If you do see other issues please let me know and/or file new bugs against pcs.
Comment 7 Chris Feist 2013-12-08 22:25:15 UTC 
Test Results: (ask-01 doesn't exist)

[root@ask-02 ~]# rpm -q pcs
pcs-0.9.90-2.el6_5.2.noarch
[root@ask-02 ~]# pcs status | grep ask-02
Online: [ ask-02 ask-03 ]
[root@ask-02 ~]# pcs cluster standby ask-01
Error: node 'ask-01' does not appear to exist in configuration
[root@ask-02 ~]# pcs cluster standby ask-02
[root@ask-02 ~]# pcs status | grep ask-02
Node ask-02: standby
[root@ask-02 ~]#
Comment 11 errata-xmlrpc 2013-12-17 10:10:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1848.html
Note You need to log in before you can comment on or make changes to this bug.