Red Hat Bugzilla – Bug 1253491
pcs status pcsd shows "Unable to authenticate" on serial console
Last modified: 2015-11-19 04:38:38 EST
Description of problem: I'm getting different output from `pcs status pcsd` whether I run it from an ssh session or the serial console. Serial console: [root@west-01 ~]# id -a uid=0(root) gid=0(root) groups=0(root) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 [root@west-01 ~]# ls -l /proc/self/fd/0 lrwx------. 1 root root 64 Aug 13 16:14 /proc/self/fd/0 -> /dev/ttyS0 [root@west-01 ~]# pcs status pcsd west-02 west-02: Unable to authenticate SSH: [root@west-01 ~]# id -a uid=0(root) gid=0(root) groups=0(root) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 [root@west-01 ~]# ls -l /proc/self/fd/0 lrwx------. 1 root root 64 Aug 13 16:15 /proc/self/fd/0 -> /dev/pts/0 [root@west-01 ~]# pcs status pcsd west-02 west-02: Online Version-Release number of selected component (if applicable): pcs-0.9.143-1.el7.x86_64 How reproducible: Easily Steps to Reproduce: 1. from serial console run: pcs status pscd Actual results: Expected results: This worked in 7.1: [root@host-054 ~]# ls -l /proc/self/fd/0 lrwx------. 1 root root 64 Aug 13 15:08 /proc/self/fd/0 -> /dev/ttyS0 [root@host-054 ~]# pcs status pcsd host-054: Online host-055: Online host-056: Online [root@host-054 ~]# rpm -q pcs pcs-0.9.137-13.el7_1.3.x86_64 Additional info:
Created attachment 1066843 [details] proposed fix
Before Fix: [root@rh71-node1 ~]# rpm -q pcs pcs-0.9.143-2.el7.x86_64 [root@rh71-node1:~]# PATH=/usr/sbin:$PATH pcs status pcsd rh71-node1: Online rh71-node2: Online [root@rh71-node1:~]# PATH=/sbin:$PATH pcs status pcsd rh71-node1: Unable to authenticate rh71-node2: Unable to authenticate After Fix: [root@rh71-node1:~]# rpm -q pcs pcs-0.9.143-3.el7.x86_64 [root@rh71-node1:~]# PATH=/usr/sbin:$PATH pcs status pcsd rh71-node1: Online rh71-node2: Online [root@rh71-node1:~]# PATH=/sbin:$PATH pcs status pcsd rh71-node1: Online rh71-node2: Online
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/RHSA-2015-2290.html