The issue that i don't fully understand is why the puppet run seems to
finish:
Oct 8 19:58:07 node2 puppet-agent[18912]:
(/Stage[main]/Task_node2__package___45_58_54_52_2dlsbwrapper4/Package[EXTR-lsbwrapper4]/ensure)
ensure changed '1.0.0-1' to '2.0.0-1'
Oct 8 19:58:12 node2 puppet-agent[18912]:
(/Stage[main]/Task_node2__package___45_58_54_52_2dlsbwrapper8/Package[EXTR-lsbwrapper8]/ensure)
ensure changed '1.0.0-1' to '0:3.0.0-1'
Oct 8 19:58:15 node2 puppet-agent[18912]:
(/File[/etc/mcollective/facts.yaml]/content) content changed
'{md5}cf91bdba62cbaa5149af42b81febbbf4' to
'{md5}994da216388be7020bade56907c701ed'
Oct 8 19:58:19 node2 puppet-agent[18912]: (/File[maincf]/seltype) seltype
changed 'etc_runtime_t' to 'etc_t'
Oct 8 19:58:22 node2 puppet-agent[18912]: Finished catalog run in 47.16
seconds
Yet after that the puppet seems to continue where it left off:
Oct 8 19:58:57 node2 puppet-agent[20580]:
(/Stage[main]/Task_node2__package___45_58_54_52_2dlsbwrapper28/Package[EXTR-lsbwrapper28]/ensure)
ensure changed '1.0.0-1' to '0:2.0.0-1'
Oct 8 19:58:58 node2 puppet-agent[20580]:
(/File[/etc/mcollective/facts.yaml]/content) content changed
'{md5}994da216388be7020bade56907c701ed' to
'{md5}d8c1cb23e367c830bc34a564d49e8353'
Oct 8 19:59:03 node2 puppet-agent[20580]: (/File[maincf]/seltype) seltype
changed 'etc_runtime_t' to 'etc_t'
Oct 8 19:59:05 node2 puppet-agent[20580]: Finished catalog run in 16.30
seconds
Not sure about this but my understanding is that a catalog run should be
sequential if there is a global lock in place?
This looks like a bug IMO. Is there any tracking done of this?
On Monday, 20 October 2014 14:11:15 UTC+1, jcbollinger wrote:
>
>
>
> On Friday, October 17, 2014 6:05:35 AM UTC-5, [email protected]
> wrote:
>>
>> I believe what Marcin is asking is how it would be possible to make
>> puppet only run once a.k.a. if puppet is already running make the second
>> run wait.
>>
>> Is there some kind of option/flag that can enable a global lock that
>> would prevent a second run of puppet not start if puppet is already running?
>>
>>
> As I wrote in my first response, different agent runs do not proceed in
> parallel on the same machine. Puppet uses a lock file to actively prevents
> it from happening. Marcin's log excerpts do not suggest otherwise.
>
> If you are determined to do so then you can defeat Puppet's protections in
> this area, but that's not what's happening in the case we're considering.
>
>
> John
>
>
--
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/0cd68401-7f2d-4cc5-9393-365d72c5553a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
