[Bug 1640919] Re: pcs cluster setup hangs

[Brian Murray]

Hello Jonathan, or anyone else affected,

Accepted pcs into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pcs/0.9.153-2ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: pcs (Ubuntu Yakkety)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
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:
  Fix Committed
Status in pcs source package in Yakkety:
  Fix Committed
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