configstore lock should use flock where possible

Bug #1467331 reported by Tim Penhey
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Tim Penhey

Bug Description

The configstore uses a lock file on disk (fslock) to protect against concurrent reads and writes of the environment file.

Even though this should only be held for a very short time during a read or write, a panic or signal while the fslock is held can cause it to be left behind.

On systems that support flock, we should use it, and fallback to the fslock only on Windows.

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: none → 1.26-alpha1
tags: added: reliability repeatability
tags: added: charmers ci
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.26-alpha1 → 1.26-alpha2
Changed in juju-core:
milestone: 1.26-alpha2 → 1.26-beta1
Changed in juju-core:
milestone: 1.26-beta1 → 2.0-alpha2
Changed in juju-core:
milestone: 2.0-alpha2 → 2.0-alpha3
Changed in juju-core:
milestone: 2.0-alpha3 → 2.0-beta4
Changed in juju-core:
milestone: 2.0-beta4 → 2.1.0
Tim Penhey (thumper)
Changed in juju-core:
status: Triaged → Fix Committed
assignee: nobody → Tim Penhey (thumper)
milestone: 2.1.0 → 2.0-beta10
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta10 → none
milestone: none → 2.0-beta10
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.