Bug 1264727

Summary:	systemctl is-active reports "unknown" after recent systemd udpate
Product:	[Fedora] Fedora	Reporter:	Paul DeStefano <prd-fedora>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	johannbg, jsynacek, lnykryn, msekleta, prd-fedora, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-22 07:20:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul DeStefano 2015-09-21 04:08:23 UTC

Description of problem:

$ /bin/systemctl is-active sshd.service
unknown


Version-Release number of selected component (if applicable):
systemd-219-21.fc22.x86_64

How reproducible:
always since update

Steps to Reproduce:
1. run 'systemctl is-active' for any service
2.
3.

Actual results:
"unknown"

Expected results:
as documented in manual pages

Comment 1 Jan Synacek 2015-09-21 07:10:58 UTC

(In reply to Paul DeStefano from comment #0)
> How reproducible:
> always since update

From which version to which version? Does the command work if you put SELinux to permissive?

Comment 2 Paul DeStefano 2015-09-21 17:08:24 UTC

Ah, okay.  I didn't reboot after systemd upgrade and, after rebooting, this symptom was gone and it wasn't broken.  I assume that is expected?  I've certainty upgraded systemd in the past and not had this problem before rebooting, but perhaps this behavior doesn't surprise others.

Not sure how best to answer your question.  dnf.rpm.log shows
CLEANUP: systemd-219-19.fc22.x86_64
right after the upgrade to this version, so I'm guessing that was the previously installed version.

Comment 3 Jan Synacek 2015-09-22 07:20:32 UTC

You should always reboot if you are updating the init daemon (systemd).

So, after reboot, this issue is not reproducible anymore.