that
> have been started by systemd. Forcing the provider to be systemd should
> restore idempotence.
>
>
>
> Sent from my Windows 10 phone
>
>
>
> *From: *Alex Harvey
> *Sent: *Sunday, March 13, 2016 7:38 PM
> *To: *Puppet Developers
> *Subject: *Re: [Pup
arted by systemd. Forcing
the provider to be systemd should restore idempotence.
Sent from my Windows 10 phone
From: Alex Harvey
Sent: Sunday, March 13, 2016 7:38 PM
To: Puppet Developers
Subject: Re: [Puppet-dev] PUP-5296
Actually no it's affecting way more than that:
[root@centos-72-x64
Actually no it's affecting way more than that:
[root@centos-72-x64 ~]# puppet apply -e 'include
profile::logstash::indexer'
Notice: Compiled catalog for centos-72-x64.wg.dir.telstra.com in
environment production in 0.54 seconds
Notice:
/Stage[main]/Profile::Logstash::Indexer/Service[logstash-
Fair enough. I have hit it twice in 11 modules that I'm using to build an
ELK solution on CentOS 7. Perhaps I'm just unlucky.
On Monday, March 14, 2016 at 12:33:29 PM UTC+11, Rob Nelson wrote:
>
> Fwiw, I'm not seeing this in any modules on EL7, I assume because all the
> packages I use suppor
Fwiw, I'm not seeing this in any modules on EL7, I assume because all the
packages I use support systemd, so it may not be that widespread across EL7
users.
On Sunday, March 13, 2016, Alex Harvey wrote:
> Hi all,
>
> I have just discovered the bug PUP-5296 using the latest Puppet 4 and the
> Pup
Hi all,
I have just discovered the bug PUP-5296 using the latest Puppet 4 and the
Puppet Labs CentOS 7 vagrant box.
This bug, reported 6 months ago, breaks idempotence in any module that
tries to use an Init-style service in the wonderful world that is Systemd.
E.g.
[root@centos-72-x64 ~]# p
