feature: charm "bug" function e.g. apport for charms

[Peter Petrakis]

It would benefit charm quality if users had an easier way to report their charm deployment failures.

$ charm bug # would...

 - determine the current env
 - scan topology
 - determine which charms failed
 - filter and present dialog "is this the charm you want to file a bug against?"
 - grab logs from env and target node if possible
 - hand off to apport

What could go wrong?
 - high number of false positives resulting from config errors
 * could create or leverage existing env checking to eliminate

[Marco Ceppi (marcoceppi)]

I don't think apport can file bugs against other distributions, in addition to this the bug command should grab configuration values for the failed service but should also scrub things like IP addresses from juju status

[Peter Petrakis (peter-petrakis)]

It's worth checking out apport more. We can do offline bug reporting, it we be kinda odd if I got an offline bug grab from a trusty box and reported it via my precise client, which then made it a precise bug.