> Description of problem:

Pcs uses 'systemctl list-unit-files' to determine whether a service exists or not. The problem here is that the booth uses unit file templates to spawn a named instance of booth (i.e. booth@booth), but these instances are never listed in a unit file list nor does the enablement status show up in list-units. While pcs correctly uses 'systemctl is-enabled' to figure out if it's enabled or not, the preceding check for service existence will never pass as booth@booth doesn't technically exist in the systemctl unit file listings. The correct way here would probably be to look for booth@ without an instance name first, and only then call the 'systemctl disable booth@booth' with the actual instance name.


> Version-Release number of selected component (if applicable):

pcs-0.9.152-9.el7.x86_64


> How reproducible:

Easily


> Steps to Reproduce:

1. systemctl enable booth@booth
2. pcs booth disable


> Actual results:

[root@duck-01 lib]# systemctl enable booth@booth
[root@duck-01 lib]# pcs booth disable
booth@booth disabled
[root@duck-01 lib]# systemctl is-enabled booth@booth
enabled


> Expected results:

[root@duck-01 lib]# systemctl enable booth@booth
[root@duck-01 lib]# pcs booth disable
booth@booth disabled
[root@duck-01 lib]# systemctl is-enabled booth@booth
disabled


> Additional info:

Oddly the 'pcs booth enable' works just fine as there is no such check present.