[PUP-10420] Observe waitforlock when acquiring the ssl lock - Puppet Jira Server

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Priority: Normal
Resolution: Fixed
Affects Version/s: None
Fix Version/s: PUP 6.16.0
Component/s: None
Labels:
- doc_reviewed

Team:
Coremunity
Sprint:
Platform Core KANBAN
Method Found:
Needs Assessment

Release Notes:
Enhancement
Release Notes Summary:

Hide
Puppet uses an ssl lockfile to ensure its certificates and keys on disk are not modified by multiple puppet processes. If puppet is unable to acquire the ssl lockfile, and the new `Puppet[:waitforlock]` setting is enabled, then puppet will wait that many seconds before retrying the ssl lock. Puppet will wait at most `Puppet[:maxwaitforlock]` seconds before giving up.

Show
Puppet uses an ssl lockfile to ensure its certificates and keys on disk are not modified by multiple puppet processes. If puppet is unable to acquire the ssl lockfile, and the new `Puppet[:waitforlock]` setting is enabled, then puppet will wait that many seconds before retrying the ssl lock. Puppet will wait at most `Puppet[:maxwaitforlock]` seconds before giving up.

QA Risk Assessment:
Needs Assessment

Description

~~PUP-8051~~ adds an option so the agent can wait for an in-progress run to finish. This ticket is to add the same functionality to the ssl state machine lock. This ticket is blocked on ~~PUP-10228~~

Attachments

Issue Links

is blocked by

PUP-10228 Puppet 6 daemons do not release ssl_lockfile

Resolved

PUP-8051 puppet agent option to wait for lock

Resolved

Activity

People

Assignee:: Josh Cooper

Reporter:: Josh Cooper

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2020/04/14 11:44 AM

Updated:: 2020/05/19 6:56 AM

Resolved:: 2020/05/18 3:30 PM