Exception caught is assumed to have strerror attribute
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juju Charm Tools |
Triaged
|
High
|
Unassigned |
Bug Description
When running charm-proof -b on something that is not recognized to be a bundle, the exception is raised but then not processed by an error in the exception handling when e.strerror does not exist.
An absurd example
[trunk]
Traceback (most recent call last):
File "/usr/bin/
load_
File "/usr/lib/
args.debug)
File "/usr/lib/
return ["FATAL: %s" % e.strerror], 200
AttributeError: 'exceptions.
It was raising the 'Not a bundle' exception, which can be found in e.message.
Changed in charm-tools: | |
milestone: | none → 1.3.1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in charm-tools: | |
milestone: | 1.3.1 → 1.3.2 |
Changed in charm-tools: | |
milestone: | 1.3.2 → 1.3.3 |
Changed in charm-tools: | |
milestone: | 1.3.3 → 1.3.4 |
Changed in charm-tools: | |
milestone: | 1.3.4 → none |