Unit seems unable to proceed after watcher died in the middle of hook execution
Bug #1532063 reported by
Charles Butler
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
I believe the state watcher is at fault here, however it could be transient datacenter issues as well - however this doesn't appear to be a recoverable issue.
When attempting to run the course of the config-changed hook the unit simply responded "Connection Closed" - upon further investigation there were complaints coming from the machine-2.log about the watcher having a closed connection, and being unable to kill the watcher.
Relevant logs attached:
| Changed in juju-core: | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in juju-core: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
[Expired for juju-core because there has been no activity for 60 days.]