Jira (PUP-8774) puppet device does not use locking

[Bas Toonk (JIRA)]

Bas Toonk created an issue

Puppet / PUP-8774 puppet device does not use locking Issue Type: Bug Affects Versions: PUP 4.10.10 Assignee: Unassigned Created: 2018/05/23 12:16 PM Priority: Major Reporter: Bas Toonk Puppet device command does not create or check for lock files. This makes it possible for several puppet device processes to run at the same time. Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Craig Gomes (JIRA)]

Craig Gomes updated an issue

Puppet / PUP-8774 puppet device does not use locking

Change By: Craig Gomes Team: Modules

Add Comment

[Thomas Honey (JIRA)]

Thomas Honey commented on PUP-8774

Re: puppet device does not use locking Hi Bas Toonk i am just following up with this, due to some of the functionality in device locking the process does not make sense. However i could see this being added as a possible new feature. IE opting into process locking. This would not be a priority, currently.  Thanks for taking the time to document this.

Add Comment

[Adam Gardner (JIRA)]

Adam Gardner commented on PUP-8774

Re: puppet device does not use locking

I think this should be revisited. While it certainly does not make sense for puppet device to be locked across all targets, it makes a lot of sense to try and protect against a single proxy running puppet device against the same target multiple times simultaneously. Just like each device target has its own cache, it should have its own lock file: /opt/puppetlabs/puppet/cache/devices/<target>/state/device_catalog_run.lock, most likely.

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-8774

puppet device does not use locking

Change By: Josh Cooper Team: Modules Network Automation

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)