debug-hooks provides incorrect path to dispatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
2.8 |
Fix Released
|
High
|
John A Meinel |
Bug Description
The help given to users during a debug-hooks session is incorrect, where juju is using the absolute path to the charm's dispatch script instead of the relative path; I'm being told to run .//var/
This is a Juju debug-hooks tmux session. Remember:
1. You need to execute hooks/actions manually if you want them to run for trapped events.
2. When you are finished with an event, you can run 'exit' to close the current window and allow Juju to continue processing
new events for this unit without exiting a current debug-session.
3. To run an action or hook and end the debugging session avoiding processing any more events manually, use:
.//var/
tmux kill-session -t plinth/0 # or, equivalently, CTRL+a d
4. CTRL+a is tmux prefix.
More help and info is available in the online documentation:
https:/
root@ip-
bash: .//var/
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: bitesize |
Changed in juju: | |
milestone: | none → 2.8-next |
Changed in juju: | |
importance: | Medium → High |
Changed in juju: | |
assignee: | nobody → John A Meinel (jameinel) |
status: | Triaged → In Progress |
milestone: | 2.8-next → 2.9-beta1 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
https:/ /github. com/juju/ juju/pull/ 11805