Jira (PUP-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.

[Ali Tukimin (JIRA)]

Title: Message Title

Ali Tukimin created an issue   Puppet / PUP-5353 Statically-enabled systemd service is treated like SysV init scripts - enabled each run. Issue Type: Bug Affects Versions: PUP 4.2.2, PUP 4.2.1 Assignee: Unassigned Created: 2015/10/12 2:32 AM Priority: Normal Reporter: Ali Tukimin Overview Statically-enabled systemd service is treated like SysV init scripts - enabled each run. One of the example is 'dbus' / 'messagebus' service which is not using SysV init script. # systemctl is-enabled dbus.service static # ls /usr/lib/systemd/system/multi-user.target.wants/|grep dbus dbus.service This is the manifest that is used in the test: package { 'dbus': ensure => installed, } $dbus_service = $::operatingsystemmajrelease ? { '5' => 'messagebus', '6' => 'messagebus', '7' => 'dbus', } service { 'messagebus': ensure => running, name => $dbus_service, enable => true, require => Package['dbus'], } Every puppet run changes enabled from 'false' to 'true': [root@pe-centos7-master ~]# puppet apply /tmp/test.pp Notice: Compiled catalog for pe-centos7-master in environment production in 0.93 seconds Notice: /Stage[main]/Main/Service[messagebus]/enable: enable changed 'false' to 'true' Notice: Applied catalog in 0.30 seconds Workaround Setting provider => redhat on services that use init scripts instead of systemd units should work around the issue. Add Comment   This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.