This bug was fixed in the package pcs - 0.9.155-1ubuntu1
---------------
pcs (0.9.155-1ubuntu1) zesty; urgency=medium
* Patch d/p/0011-Find-on-specific-directories-only.patch (LP: #1640919)
Cleaning files when destroying a cluster was taking too long in /var/lib.
Specifying /var/lib/pacemaker for "finding" leftovers solves the issue.
-- Rafael David Tinoco <rafael.tin...@canonical.com> Fri, 09 Dec 2016
03:33:30 +0000
** Changed in: pcs (Ubuntu Zesty)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1640919
Title:
pcs cluster setup hangs
Status in pcs package in Ubuntu:
Fix Released
Status in pcs source package in Xenial:
In Progress
Status in pcs source package in Yakkety:
In Progress
Status in pcs source package in Zesty:
Fix Released
Status in pcs package in Debian:
Fix Released
Bug description:
[Impact]
* PCS might take too much time when destroying a cluster.
* There is a look for leftovers over /var/lib/ using "find".
* If lxcfs is too big that might take awhile.
[Test Case]
* Install PCS
* Configure a pacemaker cluster using PCS
* Make sure /var/lib/ is huge
* Try to destroy the cluster using PCS
[Regression Potential]
* Purging leftovers could be affected.
* Almost none.
[Other Info]
Fixing together (same SRU):
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580035 (xenial)
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580045 (xenial)
And this one (yakkety & zesty)
[Original Description]
PCS cluster setup hangs, apparently due to a "find" command attempting to
search through a fuse mountpoint directory (/var/lib/lxcfs/*).
----------------->%-----------------
lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
-----------------%<-----------------
apt-cache policy pcs
pcs:
Installed: 0.9.149-1
Candidate: 0.9.149-1
Version table:
*** 0.9.149-1 500
----------------->%-----------------
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 jmclus1 uby2 uby3
Destroying cluster on nodes: uby2, uby3...
uby2: Stopping Cluster (pacemaker)...
uby3: Stopping Cluster (pacemaker)...
---setup hangs here----
The setup seems to hang because of this line in /usr/lib/python2.7
/dist-packages/pcs/cluste r.py (which attempts to delete stale cluster
configuration xml files:
os.system("find /var/lib -name '"+name+"' -exec rm -f \{\} \;")
sudo find /var/lib -name 'cib-*' 2>&1 | grep 'Permission denied' | wc -l
426
Changing this line to:
os.system("find /var/lib/pacemaker -name '"+name+"' -exec rm -f \{\} \;") to
avoid searching under /var/lib/lxcfs (the fuse mountpoint) provided a
workaround for me.
sosreport-J.Meisel.1640923-20161115104001.tar.xz -- this is an
sosreport from before installing pcs / pacemaker / corosync
sosreport-J.Meisel.1640919-20161115105845.tar.xz -- this is an
sosreport while pcs cluster setup hung
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1640919/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
