juju run command failing

Bug #1598964 reported by kumar rishabh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Unassigned
juju-core
Fix Released
Medium
Unassigned
1.25
Fix Released
Medium
Unassigned

Bug Description

I use juju 1.25.5-trusty-amd64. If I try to run a command which is supposed to timeout then the next commands also times out with higher threshold. For instance on a broken ceph cluster if I try to run `ceph health` which is supposed to not return then even a simple command like `ls -al` times out with higher value of timeout.

http://paste.ubuntu.com/18478686/

I can see the juju run process being created on the machine http://paste.ubuntu.com/18478966/. Even if I try to kill it it seems like the command queue seems to hang. Anything I am doing wrong here or is my understanding incorrect?

Tags: run
Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
tags: added: run
Revision history for this message
Cheryl Jennings (cherylj) wrote :

I suspect this is due to how we synchronized hooks / juju-run. The fix for bug 1486712 changed the locking mechanism used, and this may fix the problem.

Previously, a killed process wouldn't relinquish the lock. But the new implementation shouldn't have that problem.

Once 1.25.6 is released (hopefully soon), could you retest to see if the problem persists?

Changed in juju-core:
status: Triaged → Fix Committed
importance: Medium → High
importance: High → Medium
milestone: none → 2.0-beta12
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta12 → none
milestone: none → 2.0-beta12
Changed in juju-core:
importance: Undecided → Medium
status: New → Fix Released
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.