juju resolved reports already resolved on a unit in error state if a hook is still running

Bug #1384336 reported by Matthew Williams on 2014-10-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Wishlist
Unassigned
juju-core
Medium
Unassigned

Bug Description

Apologies for the quality of this bug report:

At the time I was called the environment was in the following state. Was in the midst of deploying openstack (trusty-icehouse)

relating ceph to nova-compute the hook reported an error and juju status reported the hook was in an error state.

Trying to do juju resolved ceph/0 responded that it couldn't mark the unit as resolved as it was already resolved. However running juju status ceph/0 reported that the hook was in error state.

Logging into the unit we observed that the hook in question was actually still running (it had hung essentially). We killed it:
ps -ef | grep "hook"

sudo kill -9 <hook-pid>

Then we tried juju resolved ceph/0 again and the hook completed.

Strawman suggestions:

It would be nice if there was some way of knowing if a hook was still running from the status page

Hand-Wave it would be nice if juju could handle this kind of situation

Abel Deuring (adeuring) on 2014-10-23
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
tags: added: hooks resolved
Curtis Hovey (sinzui) on 2014-10-28
Changed in juju-core:
importance: High → Medium
Changed in juju:
status: New → Triaged
importance: Undecided → Wishlist
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers