| Key: |
QB-1904
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Lukasz Guminski
|
| Votes: |
0
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 10/Jan/14 04:29 PM
Updated: 17/Apr/14 07:53 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
5.1.6
|
| Fix Version/s: |
5.1.8
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
After we deployed EC2 scaling in production, we noticed that when scaling of the cloud failed (due to the hitting the quota limit of running instances in EC2), the build request got removed, instead of staying in the queue. Because of this several builds which were scheduled for the last night were not executed.
This is the error that caused the problem:
AWS Error Code: InstanceLimitExceeded
AWS Error Message: Your quota allows for 0 more running instance(s). You requested at least 1
So if scaling fails (for any reason), build request should return to the queue and wait until existing resources become available.
|
|
Description
|
After we deployed EC2 scaling in production, we noticed that when scaling of the cloud failed (due to the hitting the quota limit of running instances in EC2), the build request got removed, instead of staying in the queue. Because of this several builds which were scheduled for the last night were not executed.
This is the error that caused the problem:
AWS Error Code: InstanceLimitExceeded
AWS Error Message: Your quota allows for 0 more running instance(s). You requested at least 1
So if scaling fails (for any reason), build request should return to the queue and wait until existing resources become available.
|
Show » |
|
Build requests disappear after unsuccessful scaling