Issue #7165 has been updated by Matthaus Owens.
Released in Puppet 3.2.0-rc1 ---------------------------------------- Bug #7165: If services hasn’t started yet, where possible update the file first and then start the service. https://projects.puppetlabs.com/issues/7165#change-89524 * Author: John Florian * Status: Closed * Priority: Normal * Assignee: * Category: service * Target version: 3.2.0 * Affected Puppet version: 0.25.5 * Keywords: * Branch: https://github.com/puppetlabs/puppet/pull/1459 ---------------------------------------- Given the following conditions: 1. service 'S' is currently disabled/stopped 1. config file 'F' for service 'S' is currently in state 'A' 1. puppet class 'C' calls for 'S' to be enabled/running and 'F' to be in state 'B' When puppet runs, the following currently occurs: <pre> notice: //C/File[F]/content: content changed '{md5}-A' to '{md5}-B' info: //C/File[F]: Scheduling refresh of Service[S] notice: //C/Service[S]/ensure: ensure changed 'stopped' to 'running' notice: //C/Service[S]: Triggering 'refresh' from 1 dependencies </pre> Thus, puppet sees the service is to be running and makes it so. Then it realizes that a refresh is needed and so restarts the service. The restart is unnecessary in this case. Depending on the particular service, this could be quite undesirable. Puppet should be able to recognize this case and simply start the service just once. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
