[Bug 1640919] Re: pcs cluster setup hangs

[Rafael David Tinoco]

Hello Mattia,

> For the uploads: I'm always kinda ick to upload a package introducing
a delta from debian, but well...

Well, you gotta fix what you gotta fix =).

> What I don't like are the changelogs: you're barely saying what you
did, just listing the name of the patches you added and related bugs.
I'd like to see "Add patch <name> to fix <problem>. LP: #xxxxx". This
tends to be particularly important for SRUs, where users actually go
reading the changelogs to see what they are doing to their stable
installation and figure whether the changes affects them.

I can definitely add more information if you would like. You can see
that the patches are really well explained. Some maintainers prefer a
specific format in changelog, some others. I usually use this one but I
do agree it doesn't cause any harm to add more information.

> In the xenial debdiff, you have an invalid Bug-Debian in 0007-Fix-
IPv6-bind.patch.

Tks for reviewing it, will upload a new one shortly.

-- 
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:
  Confirmed
Status in pcs source package in Xenial:
  New
Status in pcs source package in Yakkety:
  New
Status in pcs source package in Zesty:
  Confirmed
Status in pcs package in Debian:
  New

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