configstore should break fslock if time > few seconds
Bug #1500613 reported by
Tim Penhey
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Tim Penhey | ||
1.24 |
Fix Released
|
Critical
|
Tim Penhey | ||
1.25 |
Fix Released
|
High
|
Tim Penhey |
Bug Description
The filesystem lock that is used to serialize access to the config store should only ever be kept for a very short time.
However evidence shows that sometimes the client aborts and the lock is left around.
If the lock is held and the time of the lock is greater than a few seconds, the lock should be forcibly broken - and logged.
tags: | removed: tech-debt |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Tim Penhey (thumper) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
While trying to reproduce a separate, unrelated bug, I hit this lock issue.
After encountering the lock error, I cannot juju stat or juju destroy-environment (with or without --force).
Reproducer and --debug output @: paste.ubuntu. com/12621534/
http://