Comment 1 for bug 1677240

Your off today, right? :-)

> On Mar 29, 2017, at 9:09 AM, Curtis Hovey <email address hidden> wrote:
>
> Public bug reported:
>
> As seen at
> http://reports.vapour.ws/releases/issue/55badc4c749a561625b0391c
>
> This is a spike starting with build revision 5063 starting on March 28
> where tests running in AWS us-east-1 where bootstraps or deployments
> fail because of "EBS volume time out". The issue persisted for about 12
> hours, but AWS did not report a problem. The Juju revision at the start
> of the problem has nothing to do with AWS or storage.
>
> I looked at the volumes section in the aws us-east-1 console and
> discovered 287 "available" volumes dating from Feb 3. After deleting the
> "available" volumes, tests started to pass again.
>
> I suspect the issue assess_storage.py test should be deleting the
> volumes when it is done. I don't think juju should deleting these
> volumes automatically. Maybe the test needs to ask juju to delete the
> storage.
>
> ** Affects: juju-ci-tools
> Importance: High
> Status: Triaged
>
> --
> You received this bug notification because you are subscribed to juju-
> ci-tools.
> Matching subscriptions: juju-ci-tools
> https://bugs.launchpad.net/bugs/1677240
>
> Title:
> EBS volume time out: storage not cleaned up
>
> Status in juju-ci-tools:
> Triaged
>
> Bug description:
> As seen at
> http://reports.vapour.ws/releases/issue/55badc4c749a561625b0391c
>
> This is a spike starting with build revision 5063 starting on March 28
> where tests running in AWS us-east-1 where bootstraps or deployments
> fail because of "EBS volume time out". The issue persisted for about
> 12 hours, but AWS did not report a problem. The Juju revision at the
> start of the problem has nothing to do with AWS or storage.
>
> I looked at the volumes section in the aws us-east-1 console and
> discovered 287 "available" volumes dating from Feb 3. After deleting
> the "available" volumes, tests started to pass again.
>
> I suspect the issue assess_storage.py test should be deleting the
> volumes when it is done. I don't think juju should deleting these
> volumes automatically. Maybe the test needs to ask juju to delete the
> storage.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-ci-tools/+bug/1677240/+subscriptions