Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
Description
I created a spawn host with a volume that doesn't exist in AWS since it was available in the spawn host UI (it's probably a bug to allow people to try attaching volumes that don't exist in AWS) and it got stuck in provisioning (couldn't finish the user data done job because attachVolume would always fail on the AWS call). This seems to have caused amboy to refuse to run other jobs in the queue.
Attachments
Issue Links
- related to
-
EVG-7784 Host should be decommissioned if volume does not exist in AWS
-
- Closed
-