Bug 1417251 - "systemctl is-active" command reporting incorrect status when OVS related service is stopped
Summary: "systemctl is-active" command reporting incorrect status when OVS related ser...
Status: CLOSED DUPLICATE of bug 1073481
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openvswitch
Version: 7.3
Hardware: Unspecified
OS: Linux
Target Milestone: rc
: ---
Assignee: Open vSwitch development team
QA Contact: ovs-qe
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-27 16:52 UTC by Rick Alongi
Modified: 2017-01-27 17:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-01-27 17:34:34 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Rick Alongi 2017-01-27 16:52:09 UTC
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):

Kernel: 3.10.0-514.el7.x86_64
openvswitch: openvswitch-2.6.1-3.git20161206.el7fdb.x86_64 and openvswitch-2.5.0-22.git20160727.el7fdp.bz1403958.fbl.2.x86_64

How reproducible:

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.

Actual results:
systemctl is-active <service> command yields status of "unknown" for stopped ovs services.

Expected results:
systemctl is-active <service> command yields status of "inactive" for stopped ovs services.

Additional info:

Comment 1 Aaron Conole 2017-01-27 17:02:00 UTC
Is this a duplicate of bz 1073481?  I don't know that we have control over is-active - it's purely a systemd construct.

Comment 2 Rick Alongi 2017-01-27 17:34:14 UTC
Hi Aaron,

It does look like a duplicate of BZ 1073481 so it should be closed accordingly.


Comment 3 Rick Alongi 2017-01-27 17:34:34 UTC

*** This bug has been marked as a duplicate of bug 1073481 ***

Note You need to log in before you can comment on or make changes to this bug.