Package: pcs Version: 0.9.155-1 Severity: important Tags: patch -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I'm working on the following Ubuntu bugs: https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580035 https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580045 https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1640923 https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1640919 And bugs LP: #1640923 and LP: #1640919 should be fixed in Debian. I'm attaching package debdiffs for both bugs as a fix suggestion. I'm also proposing the same patch to Zesty, Yakkety & Xenial. Upstream patch for LP: #1640919 was already accepted: https://github.com/ClusterLabs/pcs/pull/119 ## Problems Description ## LP: #1640919 - pcs cluster auth does not generate "tokens" file $ sudo pcs cluster auth cluster01 cluster02 -u hacluster Password: cluster01: Authorized cluster02: Authorized $ sudo ls -l /var/lib/pcsd/tokens ls: cannot access '/var/lib/pcsd/tokens': No such file or directory If corosync and pacemaker are stopped and /etc/corosync.conf is removed, then /var/lib/pcsd/tokens gets created successfully. $ systemctl stop pacemaker $ systemctl stop corosync $ sudo rm /etc/corosync/corosync.conf $ sudo pcs cluster auth cluster01 cluster02 -u hacluster Password: cluster01: Authorized cluster02: Authorized ls -l /var/lib/pcsd/tokens - -rw------- 1 root root 168 Nov 10 11:54 /var/lib/pcsd/tokens LP: #1640919 - pcs cluster setup hangs Edit PCS cluster setup hangs when cleaning up old cluster configurations, apparently due to a "find" command attempting to search through a fuse mountpoint directory (/var/lib/lxcfs/*). $ sudo pcs cluster setup --name cluster cluster01 cluste02 Destroying cluster on nodes: cluster01, cluster02... cluster01: Stopping Cluster (pacemaker)... cluster02: Stopping Cluster (pacemaker)... - ---setup hangs here---- The setup seems to hang because of this line in /usr/lib/python2.7/dist-packages/pcs/cluster.py (which attempts to delete stale cluster configuration xml files: os.system("find /var/lib -name '"+name+"' -exec rm -f \{\} \;") I'm attaching the fixes soon, following the bug opening. -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYR2fHAAoJEB8C+bMrFbSZLRUQAJ9xspeoXOsBcfdMv3XSWsj5 hVJnpZsLO/XuZeSswyigMNCSqihzK1ILHBWmBzCOAOnkI8XKC65uZ4MWtFwPmt/C QuxOEQ46XV212YfYY2+HKEJodHwf6O6dxEkLeVmkM7wbclaijPDmnFSmJTNrIDv5 OQDzUFf7XUA0Id8e3DyWG73UayEx2A449kkkbCAJZzIomykY2PE8yE8IyTMg0W+g R4t6roEm08pqMSGLqyiRwUVQY7qiFPEO25p1fogOxKG+ZiUCd0LJiCMY5kwRMU2Q d+rUNkBSkYRII4bMMCu0nNheDVVXsJ8S6uDHfFTTNPd7WVC4+8EXZFWj2LPZbowI wMvC6dwAdw8yJCQtCKVkHtbyPNQaF2z1sNrsqqRGmbvxTX3L+hUS27ufm2qGKYMp B+Zv6h7nRUIgWCYdQUZG0W3j/T2DT8oxUfvivaTp8pl3jw3tZtI+x83W8y6sovGN oPYmsfrveuLMql7tBaKP8jy7H3C8QlzX2bfl+FXWJ2GS6eb7witEow/F7pi2NT2t XWFfkvrrTRvrck8VhMJZDrsUoXOpo5caxHtW7UJ4tiex/Jp3As340KMi0OAMTV9X K/ErCQs27WbRagOIwwNHDpHhsIVD9VO09xf8RXWQOyEDQnJ8gFGjw9M3X3ZkwkAn wmR4HWvoRZ4nEdhaHU4D =+SWU -----END PGP SIGNATURE-----
