provider/ec2: bootstrap fails with "failed to bootstrap environment: cannot start bootstrap instance: tagging root disk: timed out waiting for EBS volume to be associated"

Bug #1501559 reported by Andrew Wilkins on 2015-10-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
High
Andrew Wilkins
1.25
High
Andrew Wilkins

Bug Description

See:
    http://reports.vapour.ws/releases/3124/job/aws-deploy-trusty-amd64-on-wily-amd64/attempt/220

I don't think there's much we can do apart from increasing the timeout. We're currently only waiting for 5 seconds, which evidently is not enough time for the root disk to be provisioned and attached to the instance.

Note, CI matches this to lp:1479546, which is wrong. They are separate issues; this one is specifically to do with tagging root disks, whereas the other one was about volume provisioning.

Andrew Wilkins (axwalk) on 2015-10-01
Changed in juju-core:
assignee: nobody → Andrew Wilkins (axwalk)
Ian Booth (wallyworld) on 2015-10-01
Changed in juju-core:
milestone: 1.25-beta2 → 1.26-alpha1
Andrew Wilkins (axwalk) on 2015-10-01
Changed in juju-core:
status: Triaged → In Progress
Andrew Wilkins (axwalk) on 2015-10-02
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui) on 2015-10-23
tags: added: tech-debt
Curtis Hovey (sinzui) on 2015-11-03
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers