Issue #10065 has been updated by John Florian. Status changed from Unreviewed to Duplicate
This is a duplicate of #7165. ---------------------------------------- Bug #10065: Puppet should not refresh a service it just started https://projects.puppetlabs.com/issues/10065 Author: Chip Schweiss Status: Duplicate Priority: Normal Assignee: Category: service Target version: Affected Puppet version: 2.6.9 Keywords: Branch: If notify is called on a service that was stopped when the puppet run starts, puppet will start the service and immediately try to stop and start it. <pre> notice: /Stage[main]/Postgresql9::Server/Service[postgresql-9.0]/ensure: ensure changed 'stopped' to 'running' err: /Stage[main]/Postgresql9::Server/Service[postgresql-9.0]: Failed to call refresh: Could not stop Service[postgresql-9.0]: Execution of '/sbin/service postgresql-9.0 stop' returned 1: at /etc/puppetmaster/devel/modules/postgresql9/manifests/init.pp:76 </pre> init.pp: <pre> .... service { "postgresql-9.0": ensure => running, enable => true, hasstatus => true, require => Exec["init_pg_server"]; } .... </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
