On 14/03/16 00:59, Alex Harvey 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 for raising the awareness, seems like that ticket had fallen
through the cracks. I assigned the ticket to the Client Platform Team
and pinged Kylo Ginsberg.
- henrik
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
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/56E60ED1.9020609%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.
