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 1394857 - pcs should depend on cman because of cman_tool
Summary: pcs should depend on cman because of cman_tool
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.9
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Ivan Devat
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 15:19 UTC by Radek Steiger
Modified: 2017-03-21 11:04 UTC (History)
5 users (show)

Fixed In Version: pcs-0.9.155-2.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 11:04:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0707 0 normal SHIPPED_LIVE pcs bug fix update 2017-03-21 12:40:33 UTC

Description Radek Steiger 2016-11-14 15:19:27 UTC
> Description of problem:

If cman is not installed on a RHEL6 system together with pcs, the pcs authentication will never really succeed although it reports otherwise. 


> Version-Release number of selected component (if applicable):

pcs-0.9.155-1.el6.x86_64


> How reproducible:

Always


> Steps to Reproduce:

1. install the pcs package without installing cman
2. start the pcsd daemon
3. authenticate locally or remotely 'pcs cluster auth <address>'
4. verify authentication with 'pcs status pcsd <address>'


> Actual results:

[root@virt-011 ~]# pcs status pcsd virt-011
  virt-011: Unable to authenticate


> Expected results:

[root@virt-011 ~]# pcs status pcsd virt-011
virt-011: Authorized


> Additional info:

[root@virt-011 ~]# ll /var/lib/pcsd/tokens
ls: cannot access /var/lib/pcsd/tokens: No such file or directory

[root@virt-011 ~]# pcs cluster auth virt-011 -uhacluster
Password: 
virt-011: Authorized

[root@virt-011 ~]# pcs status pcsd virt-011
  virt-011: Unable to authenticate

[root@virt-011 ~]# ll /var/lib/pcsd/tokens
ls: cannot access /var/lib/pcsd/tokens: No such file or directory

[root@virt-011 ~]# pcs cluster auth virt-011 -uhacluster --debug
Password: 
Running: /usr/bin/ruby -I/usr/lib/pcsd/ /usr/lib/pcsd/pcsd-cli.rb auth
--Debug Input Start--
{"username": "hacluster", "local": false, "nodes": ["virt-011"], "password": "password", "force": false}
--Debug Input End--
Return Value: 0
--Debug Output Start--
{
  "status": "ok",
  "data": {
    "auth_responses": {
      "virt-011": {
        "token": "6a98ec2e-fd17-431d-8e17-9353e86839ed",
        "status": "ok"
      }
    },
    "sync_responses": {
    },
    "sync_successful": true,
    "sync_nodes_err": [

    ]
  },
  "log": [
    "I, [2016-11-14T16:14:14.816115 #27063]  INFO -- : PCSD Debugging enabled\n",
    "D, [2016-11-14T16:14:14.816215 #27063] DEBUG -- : Detected RHEL 6\n",
    "I, [2016-11-14T16:14:14.816274 #27063]  INFO -- : Running: /usr/sbin/corosync-objctl cluster\n",
    "I, [2016-11-14T16:14:14.816333 #27063]  INFO -- : CIB USER: hacluster, groups: \n",
    "D, [2016-11-14T16:14:14.819064 #27063] DEBUG -- : []\n",
    "D, [2016-11-14T16:14:14.819137 #27063] DEBUG -- : [\"Failed to initialize the objdb API. Error 6\\n\"]\n",
    "D, [2016-11-14T16:14:14.819199 #27063] DEBUG -- : Duration: 0.002741s\n",
    "I, [2016-11-14T16:14:14.819305 #27063]  INFO -- : Return Value: 1\n",
    "I, [2016-11-14T16:14:14.823707 #27063]  INFO -- : SRWT Node: virt-011 Request: check_auth\n",
    "E, [2016-11-14T16:14:14.823847 #27063] ERROR -- : Unable to connect to node virt-011, no token available\n",
    "I, [2016-11-14T16:14:15.098971 #27063]  INFO -- : Running: /usr/sbin/pcs status nodes corosync\n",
    "I, [2016-11-14T16:14:15.099117 #27063]  INFO -- : CIB USER: hacluster, groups: \n",
    "D, [2016-11-14T16:14:15.598652 #27063] DEBUG -- : [\"No such file or directory\\n\"]\n",
    "D, [2016-11-14T16:14:15.598850 #27063] DEBUG -- : [\"Error: unable to locate command: /usr/sbin/cman_tool\\n\"]\n",
    "D, [2016-11-14T16:14:15.598909 #27063] DEBUG -- : Duration: 0.499524s\n",
    "I, [2016-11-14T16:14:15.599080 #27063]  INFO -- : Return Value: 1\n",
    "I, [2016-11-14T16:14:15.599677 #27063]  INFO -- : Sending config 'tokens' version 1 2b271c6bc3fa4036869556c5ca2f33e485afffa7 to nodes: \n"
  ]
}
--Debug Output End--
virt-011: Authorized

Comment 3 Tomas Jelinek 2016-11-15 14:33:39 UTC
cman_tool is also required for reloading cluster.conf and stopping cluster nodes.

Comment 7 errata-xmlrpc 2017-03-21 11:04:53 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.

https://rhn.redhat.com/errata/RHBA-2017-0707.html


Note You need to log in before you can comment on or make changes to this bug.