[Bug 915506] Re: juju-log and relation-set outputs {}

[Clint Byrum]

** Description changed:

+ == 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/doc/juju/examples local:mysql
+ 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...

** Also affects: juju (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: juju (Ubuntu)
       Status: New => Fix Released

** Also affects: juju (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Changed in: juju (Ubuntu Precise)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/915506

Title:
  juju-log and relation-set outputs {}

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/915506/+subscriptions