The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Bug #10065

Puppet should not refresh a service it just started

Added by Chip Schweiss almost 4 years ago. Updated almost 4 years ago.

Status:DuplicateStart date:10/13/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:service
Target version:-
Affected Puppet version:2.6.9 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com


Description

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.

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

init.pp:

....
service {
    "postgresql-9.0":
        ensure => running,
        enable => true,
        hasstatus => true,
        require => Exec["init_pg_server"];
}
....

History

#1 Updated by John Florian almost 4 years ago

  • Status changed from Unreviewed to Duplicate

This is a duplicate of #7165.

Also available in: Atom PDF