feature: charm "bug" function e.g. apport for charms
Bug #1280444 reported by
Peter Petrakis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juju Charm Tools |
Triaged
|
Wishlist
|
Marco Ceppi |
Bug Description
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
Changed in charm-tools: | |
milestone: | 1.3.0 → 1.4.0 |
Changed in charm-tools: | |
importance: | High → Wishlist |
milestone: | 1.4.0 → none |
To post a comment you must log in.
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