My guess, based on similar behavior in Chef, is that, for SysV init scripts,
it's trying to use the SysV init system directly either via the service command
or by calling the scripts themselves directly. Unfortunately, this doesn’t play
super nicely with SysV init scripts 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: [Puppet-dev] PUP-5296
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-indexer]/enable:
enable changed 'false' to 'true'
Notice: Applied catalog in 0.99 seconds
[root@centos-72-x64 ~]# puppet apply -e 'include profile::logstash::shipper'
Notice: Compiled catalog for centos-72-x64.wg.dir.telstra.com in environment
production in 0.47 seconds
Notice:
/Stage[main]/Profile::Logstash::Shipper/Service[logstash-shipper]/enable:
enable changed 'false' to 'true'
Notice: Applied catalog in 0.92 seconds
[root@centos-72-x64 ~]# puppet apply -e 'include profile::redis'
Notice: Compiled catalog for centos-72-x64.wg.dir.telstra.com in environment
production in 0.73 seconds
Notice:
/Stage[main]/Disable_transparent_hugepage/Service[disable-transparent-hugepage]/enable:
enable changed 'false' to 'true'
Notice: Applied catalog in 1.79 seconds
[root@centos-72-x64 ~]# puppet apply -e 'include profile::kibana4'
Notice: Compiled catalog for centos-72-x64.wg.dir.telstra.com in environment
production in 0.44 seconds
Notice: /Stage[main]/Kibana4::Service/Service[kibana4]/enable: enable changed
'false' to 'true'
Notice: Applied catalog in 0.72 seconds
[root@centos-72-x64 ~]# puppet resource service network enable=true
Notice: /Service[network]/enable: enable changed 'false' to 'true'
service { 'network':
ensure => 'running',
enable => 'false',
}
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 support systemd, so it may not be that widespread across EL7
users.
On Sunday, March 13, 2016, Alex Harvey <alexh...@gmail.com> wrote:
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 ~]# puppet apply /tmp/apply_manifest.pp.ZEj2Kr
Notice: Compiled catalog for centos-72-x64.wg.dir.telstra.com in environment
production in 2.10 seconds
Notice: /Stage[main]/Kibana4::Service/Service[kibana4]/enable: enable changed
'false' to 'true'
Notice: Applied catalog in 18.70 seconds
[root@centos-72-x64 ~]# puppet apply /tmp/apply_manifest.pp.ZEj2Kr
Notice: Compiled catalog for centos-72-x64.wg.dir.telstra.com in environment
production in 2.26 seconds
Notice: /Stage[main]/Kibana4::Service/Service[kibana4]/enable: enable changed
'false' to 'true'
Notice: Applied catalog in 18.61 seconds
A workaround might be to raise a PR to add optional provider overrides for
every module in the world that tries to manage a SysV style service on a
platform.
But the bug report indicates that we already know what the fix is for this bug?
Can't we just fix it?
Thanks,
Alex
--
Partner
RAZOR Consulting
t: +61 409 665 227
w: http://razorconsulting.com.au
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/47bb57e7-30ef-4494-8230-c326829f740d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Rob Nelson
rnel...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/8917427f-b679-49df-8ad5-0d32387b802a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/56e65570.9448620a.fe8ed.6841%40mx.google.com.
For more options, visit https://groups.google.com/d/optout.
