Description of problem:
systemctl is-active <service> reports as "unknown" rather than "inactive" when ovs related systemd services have been stopped.
Version-Release number of selected component (if applicable):
openvswitch: openvswitch-2.6.1-3.git20161206.el7fdb.x86_64 and openvswitch-2.5.0-22.git20160727.el7fdp.bz1403958.fbl.2.x86_64
Steps to Reproduce:
1. systemctl restart openvswitch.service
2. systemctl stop openvswitch.service
3. systemctl is-active openvswitch.service --> reports as "unknown" instead of "inactive"
4. systemctl is-active ovs-vswitchd.service --> reports as "unknown" instead of "inactive"
5. systemctl is-active ovsdb-server.service --> reports as "unknown" instead of "inactive"
Repeat steps 1 and 2 (substituting ovs-vswitchd-service and ovsdb-server.service in Step 2) and results for Steps 3-5 are the same in each case.
NOTE: The CORRECT STATUS IS REPORTED via systemctl status <service>. It is just the systemctl is-active <service> command that is yielding the wrong value.
systemctl is-active <service> command yields status of "unknown" for stopped ovs services.
systemctl is-active <service> command yields status of "inactive" for stopped ovs services.
Is this a duplicate of bz 1073481? I don't know that we have control over is-active - it's purely a systemd construct.
It does look like a duplicate of BZ 1073481 so it should be closed accordingly.
*** This bug has been marked as a duplicate of bug 1073481 ***