check_resource_systemd might break under certain conditions

[Michele Baldessari]

During upgrade we called "check_resource_systemd "memcached" stopped 600".
Interestingly enough this broke at least once for me (likely due to a systemd bug). In short, "systemctl is-active memcached" seems to not work
correctly under some conditions. For example:

[root@overcloud-controller-0 heat-config-script]# systemctl status memcached
● memcached.service - Memcached
   Loaded: loaded (/usr/lib/systemd/system/memcached.service; disabled; vendor preset: disabled)
   Active: active (running) since Fri 2016-09-23 21:46:36 UTC; 8s ago
 Main PID: 25285 (memcached)
   CGroup: /system.slice/memcached.service
           └─25285 /usr/bin/memcached -u memcached -p 11211 -m 7383 -c 8192 -l 172.16.2.9 -U 11211 -t 4 >> /var/log/memcached.log 2>&1

Sep 23 21:46:36 overcloud-controller-0 systemd[1]: Started Memcached.
Sep 23 21:46:36 overcloud-controller-0 systemd[1]: Starting Memcached...
[root@overcloud-controller-0 heat-config-script]# systemctl is-active memcached
active
[root@overcloud-controller-0 heat-config-script]# systemctl stop memcached
[root@overcloud-controller-0 heat-config-script]# systemctl is-active memcached
unknown

This breaks at least check_resource_systemd because it will bail with:
ERROR - memcached not found to be systemd managed.

For now I set the importance to medium, because I think I can work around it.

[Michele Baldessari (michele)]

I have seen this issue with the mongod service as well. I wonder if this has to do with systemd and pacemaker interaction (i.e. when pacemaker adds a drop-in file) and systemd gets confused?

[Emilien Macchi (emilienm)]

This bug was last updated over 180 days ago, as tripleo is a fast moving project and we'd like to get the tracker down to currently actionable bugs, this is getting marked as Invalid. If the issue still exists, please feel free to reopen it.