cmd/juju: debug-hooks cannot debug the install hook
Bug #1221501 reported by
Dave Cheney
This bug affects 6 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
| juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
debug-hooks cannot hook the install hook. This is a regression from juju 0.7
Revision history for this message
| Kapil Thangavelu (hazmat) wrote | #1 |
| Changed in juju-core: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| tags: | added: debug-hooks |
| Changed in juju-core: | |
| importance: | High → Medium |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #2 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 2.1.0 |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
| Changed in juju: | |
| milestone: | 2.1-rc2 → none |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Pyjuju used state to represent debug-hooks. The unit state exists as soon as add-unit/deploy is done, and then pyjuju could attach the debug flag to the unit state. The unit agent (and its machine) would come up and observe/act upon its state, and process debug-hooks before entering into its state machine. With juju-core there is no use of state for debug hooks, and no coordination around the unit's statemachine, its a soley a race of the existence of the tmux session before a hook executes. This makes it very hard to catch install hooks or start hooks (depending on how long the install hook took).