Issue #7165 has been updated by Lukáš Zapletal.
Having the same issue with configuring MongoDB:
130205-20:22:39 notice: /File[/var/lib/mongodb/journal]/ensure: created
130205-20:22:39 debug: Exec[mongo-journal-prealloc](provider=posix):
Executing '/bin/dd if=/dev/zero of=/var/lib/mongodb/journal/prealloc.0 bs=1M
count=1K && /bin/dd if=/dev/zero of=/var/lib/mongodb/journal/prealloc.1 bs=1M
count=1K && /bin/dd if=/dev/zero of=/var/lib/mongodb/journal/prealloc.2 bs=1M
count=1K && chmod 600 /var/lib/mongodb/journal/prealloc* && chown
mongodb:mongodb /var/lib/mongodb/journal/prealloc*'
130205-20:22:39 debug: Executing '/bin/dd if=/dev/zero
of=/var/lib/mongodb/journal/prealloc.0 bs=1M count=1K && /bin/dd if=/dev/zero
of=/var/lib/mongodb/journal/prealloc.1 bs=1M count=1K && /bin/dd if=/dev/zero
of=/var/lib/mongodb/journal/prealloc.2 bs=1M count=1K && chmod 600
/var/lib/mongodb/journal/prealloc* && chown mongodb:mongodb
/var/lib/mongodb/journal/prealloc*'
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1024+0
records in
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1024+0
records out
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1073741824
bytes (1.1 GB) copied, 5.83921 s, 184 MB/s
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1024+0
records in
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1024+0
records out
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1073741824
bytes (1.1 GB) copied, 22.8184 s, 47.1 MB/s
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1024+0
records in
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1024+0
records out
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: 1073741824
bytes (1.1 GB) copied, 20.9342 s, 51.3 MB/s
130205-20:23:10 notice:
/Stage[main]/Mongodb::Config/Exec[mongo-journal-prealloc]/returns: executed
successfully
130205-20:23:10 debug: Service[mongod](provider=redhat): Executing
'/usr/sbin/service-wait mongod status'
130205-20:23:10 debug: Puppet::Type::Service::ProviderRedhat: Executing
'/sbin/chkconfig mongod'
130205-20:23:10 debug: Service[mongod](provider=redhat): Executing
'/usr/sbin/service-wait mongod start'
130205-20:23:17 debug: Puppet::Type::Service::ProviderRedhat: Executing
'/sbin/chkconfig mongod'
130205-20:23:17 debug: Puppet::Type::Service::ProviderRedhat: Executing
'/sbin/chkconfig mongod on'
130205-20:23:17 notice:
/Stage[main]/Mongodb::Service/Service[mongod]/ensure: ensure changed 'stopped'
to 'running'
130205-20:23:17 debug: Service[mongod](provider=redhat): Executing
'/usr/sbin/service-wait mongod status'
130205-20:23:17 debug: Service[mongod](provider=redhat): Executing
'/usr/sbin/service-wait mongod restart'
130205-20:23:27 notice: /Stage[main]/Mongodb::Service/Service[mongod]:
Triggered 'refresh' from 1 events
The code:
https://github.com/Katello/katello/tree/master/katello-configure/modules/mongodb/manifests
It's Puppet 2.6 from EPEL and I know this is the old one, but as guys describes
it is still not fixed, just adding the log here for case.
----------------------------------------
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-82651
Author: John Florian
Status: Needs More Information
Priority: Normal
Assignee: eric sorenson
Category: service
Target version:
Affected Puppet version: 0.25.5
Keywords:
Branch:
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.
