juju-log and relation-set outputs {}
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Low
|
Benjamin Saller | ||
juju (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
== SRU Justification ==
=== Impact ===
This causes some charms to have to add complex output control logic for calling juju-log.
=== Test Case ===
1. juju bootstrap
2. juju deploy --repository /usr/share/
3. juju debug-hooks mysql/0
4. upon seeing the install window open, type 'juju-log foo'. Affected versions will show '{}', unaffected versions will return without printing anything.
=== Dev Fix ===
This was fixed in upstream commit 534
=== Regression Potential ===
Low. Charms *MIGHT* have been written in a way where not printing {} would cause issues, but this is very unlikely and is easy to work around.
== Original Bug Description ==
using juju with lxc provider on oneiric.
Enter debugging session on a unit with 'juju debug-hooks' and catch an event.
At the console type 'juju-log "test"'
The standard output receives a {}
This is really anoying if you called juju-log within a function which standard output is important to you...
Related branches
- Juju Engineering: Pending requested
-
Diff: 52 lines (+11/-4)2 files modifiedjuju/hooks/commands.py (+4/-1)
juju/hooks/tests/test_invoker.py (+7/-3)
Changed in juju: | |
milestone: | none → florence |
Changed in juju: | |
milestone: | florence → galapagos |
Changed in juju: | |
assignee: | nobody → Benjamin Saller (bcsaller) |
Changed in juju: | |
milestone: | galapagos → honolulu |
status: | Confirmed → In Progress |
Changed in juju: | |
status: | In Progress → Fix Released |
description: | updated |
Changed in juju (Ubuntu): | |
status: | New → Fix Released |
Changed in juju (Ubuntu Precise): | |
status: | New → Triaged |
strace of the call to juju-log on the lxc container