Jira (PUP-6436) Puppet run doesn't fail when Systemd fails to start service

[Martin Caslavsky (JIRA)]

Title: Message Title

Martin Caslavsky created an issue   Puppet / PUP-6436 Puppet run doesn't fail when Systemd fails to start service Issue Type: Bug Assignee: Unassigned Created: 2016/06/24 4:35 AM Environment: EL7 Priority: Normal Reporter: Martin Caslavsky Lets have Systemd unit file for a simple service, but pass wrong argument to ExecStart command: --foo. /usr/lib/systemd/system/ncat.service [Unit] Description=Ncat [Service] ExecStart=/bin/ncat --keep-open --listen 5000 --sh-exec 'xargs -n1 echo' --foo [Install] WantedBy=multi-user.target Run: # puppet apply -e 'service {"ncat": ensure => running }' Notice: /Stage[main]/Main/Service[ncat]/ensure: ensure changed 'stopped' to 'running' Because of the wrong argument the service is not started however puppet finishes successfully. The thing is the command systemctl start always exits with 0 exit code no matter the start was successful or not. Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.