Jira (PUP-4993) systemd thinks 'activating' services are 'stopped'

Ryan Gordon (JIRA)

unread,

Aug 3, 2015, 3:30:05 PM8/3/15

to puppe...@googlegroups.com

Ryan Gordon created an issue

Puppet /

PUP-4993

systemd thinks 'activating' services are 'stopped'

Issue Type:	Bug
Affects Versions:	PUP 4.2.1
Assignee:	Unassigned
Created:	2015/08/03 12:29 PM
Priority:	Normal
Reporter:	Ryan Gordon

> /bin/systemctl is-active servicetest123
activating
> echo $?
3

Puppet run:
Notice: /Stage[main]/Service[servicetest123]/ensure: ensure changed 'stopped' to 'running'

Expected behavior: A return code of 3 from is-active, is also considered "running" in puppet

Add Comment

This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)

Moses Mendoza (JIRA)

unread,

May 17, 2017, 2:38:03 PM5/17/17

to puppe...@googlegroups.com

Moses Mendoza updated an issue

Puppet /

PUP-4993

systemd thinks 'activating' services are 'stopped'

Change By:	Moses Mendoza
Team:	Agent

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

Moses Mendoza (JIRA)

unread,

May 17, 2017, 2:38:03 PM5/17/17

to puppe...@googlegroups.com

Moses Mendoza updated an issue

Puppet /

PUP-4993

systemd thinks 'activating' services are 'stopped'

Change By:	Moses Mendoza
Labels:	triaged

Add Comment

Branan Riley (JIRA)

unread,

May 10, 2018, 7:10:02 PM5/10/18

to puppe...@googlegroups.com

Branan Riley updated an issue

Puppet /

PUP-4993

systemd thinks 'activating' services are 'stopped'

Change By:	Branan Riley
Labels:	linux service systemd triaged type_and_provider

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Josh Cooper (Jira)

unread,

Jun 9, 2021, 9:42:01 PM6/9/21

to puppe...@googlegroups.com

Josh Cooper commented on

PUP-4993

Re: systemd thinks 'activating' services are 'stopped'

It's important that puppet wait for the service to reach the 'activated' state before moving onto the next resource so we can't assume 'activating' is the same as 'running'. It is possible puppet should wait/retry for the service to finish (such as if the service is restarted by something outside of puppet while it's running)... It'd be good to make this consistent as we may have the same issue on other platforms like windows, which have a 'starting' state.