Fix: "find" should run only in specific directories

[rafaeldtinoco]

Some users reported that running find over "/var/lib" for cleanup
purposes can take too long depending on what you have installed.
A particular example was having "lxcfs" fuse mounted in /var/lib.
That can make the search for cluster leftovers to take quite some
time, making user to believe the process has hang.

[rafaeldtinoco]

This fix is coming specifically from:

https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1640919

Meanwhile I'm also fixing 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

If possible, could u please provide a fast answer if this commit can be accepted or not ? Tomorrow I'll propose upstream package fixes (Debian) to backport this to Ubuntu later on.

Thank you very much.

[tomjelinek]

Thanks for the patch!

[rafaeldtinoco]

inaddy@(cluster01):~$ sudo pcs cluster destroy
Shutting down pacemaker/corosync services...
Killing any remaining services...
Removing all cluster configuration files...
find: ‘/var/lib/{pacemaker,corosync}’: No such file or directory
find: ‘/var/lib/{pacemaker,corosync}’: No such file or directory
find: ‘/var/lib/{pacemaker,corosync}’: No such file or directory
find: ‘/var/lib/{pacemaker,corosync}’: No such file or directory
find: ‘/var/lib/{pacemaker,corosync}’: No such file or directory
find: ‘/var/lib/{pacemaker,corosync}’: No such file or directory
find: ‘/var/lib/{pacemaker,corosync}’: No such file or directory

{} isn't interpreted in os.system(). My bad. Fixing it and proposing merge again.

[rafaeldtinoco]

Please check #120