EBS will not create two more volumes right now, so don't scale up that big.

[kurtwheeler]

Issue Number

N/A came up while trying to deploy #1520

Purpose/Implementation Notes

Three deploys in a row have failed with:

Error: Error applying plan:

2 error(s) occurred:

* aws_ebs_volume.data_refinery_ebs[11]: 1 error(s) occurred:

* aws_ebs_volume.data_refinery_ebs.11: Error waiting for Volume (vol-0fa225699638207db) to become available: timeout while waiting for state to become 'available' (last state: 'creating', timeout: 5m0s)
* aws_ebs_volume.data_refinery_ebs[10]: 1 error(s) occurred:

* aws_ebs_volume.data_refinery_ebs.10: Error waiting for Volume (vol-04ebd4369d9630189) to become available: timeout while waiting for state to become 'available' (last state: 'creating', timeout: 5m0s)

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

I can see the EBS volumes in the AWS console, they are in fact stuck at creating and will not progress from there. My best guess is a bug in EBS.

[davidsmejia]

Ok