Running several 'juju run' commands in parrallel triggers lock timeout failures
Bug #1437177 reported by
Stuart Bishop
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juju Wait Plugin |
Fix Released
|
Undecided
|
Adam Israel | ||
| juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
I was launching up to 6 'juju run' commands at the same time against different units in the same service. Some of these processes would fail with 'ERROR cannot read info: lock timeout exceeded', return code 1.
juju run --timeout=21600s --unit postgresql/0 sudo tail -1 /var/log/
Related branches
| Changed in juju-wait: | |
| assignee: | nobody → Adam Israel (aisrael) |
| status: | New → Fix Committed |
| Changed in juju-wait: | |
| status: | Fix Committed → Fix Released |
| Changed in juju-core: | |
| status: | New → Won't Fix |
To post a comment you must log in.
