ErroredUnit lacks details for good matches

Bug #1576505 reported by Martin Packman on 2016-04-29
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-ci-tools
Critical
Nicholas Skaggs

Bug Description

The ErroredUnit exception in jujupy does not have enough details to make for good matching rules in juju reports. At present we have one generic rule, which can have many causes:

<http://reports.vapour.ws/releases/rules/600>
<http://reports.vapour.ws/releases/issue/557ae153749a560de7ad6952>

In order to actually find out what happened, you have to look further down in the log to the status output, for example:

<http://reports.vapour.ws/releases/3933/job/native-deploy-landscape-gce/attempt/76>

2016-04-28 23:42:22 ERROR 0 is in state error
Traceback (most recent call last):
  ...
ErroredUnit: 0 is in state error
2016-04-28 23:42:22 INFO juju --debug show-status ...
...
machines:
  "0":
    juju-status:
      current: error
      message: 'sending new instance request: GCE operation "operation-1461886933398-53194135df1f1-e5e64d0f-d83caa45"
        failed'
      since: 28 Apr 2016 23:42:22Z
    instance-id: pending

Related branches

Aaron Bentley (abentley) on 2016-06-02
Changed in juju-ci-tools:
importance: High → Critical
assignee: nobody → Nicholas Skaggs (nskaggs)
Changed in juju-ci-tools:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers