Better error reporting on AWS failures

Bug #1827409 reported by Kenneth Koski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AWS Integrator Charm
Fix Released
Undecided
Unassigned

Bug Description

As a follow-up to https://bugs.launchpad.net/charm-aws-integrator/+bug/1821785, it would be nice if the aws-integrator charm could report errors a little better. Right now if there's an error like hitting the subnet tag limit, juju status just shows "error while granting requests; check credentials and debug-log", and CI processes won't necessarily be dumping the debug log anywhere handy, so the deploy just times out and there's no great introspection. If `juju status` were instead able to show something like the exception from debug-log, that would be much more helpful:

    charms.layer.aws.AWSError: An error occurred (TagLimitExceeded) when calling the CreateTags <...> too many Tags

Cory Johns (johnsca)
Changed in charm-aws-integrator:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.