-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛✨EC2 machine creation: try to create at least 1 machine #5408
🐛✨EC2 machine creation: try to create at least 1 machine #5408
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice 💯
Is there any useful log message reported back (through the API server) if we run out of quota? |
@mguidon :
Not through the api-server though |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5408 +/- ##
=========================================
Coverage 87.5% 87.5%
=========================================
Files 1322 959 -363
Lines 54234 42418 -11816
Branches 1175 228 -947
=========================================
- Hits 47479 37146 -10333
+ Misses 6506 5223 -1283
+ Partials 249 49 -200
Flags with carried forward coverage won't be shown. Click here to find out more.
|
aeadf1d
to
eeb6fce
Compare
5add2e3
to
7e99519
Compare
7e99519
to
62d1eb9
Compare
|
What do these changes do?
BEFORE: The autoscaling would try to create up to
EC2_INSTANCES_MAX_INSTANCES
instances and fail to do so if for example the EC2 number of machines quota is exceeded.AFTER: The autoscaling will try to create between 1 and
EC2_INSTANCES_MAX_INSTANCES
instances. so if the quota is exceeded, EC2 will try to create between 1 and the asked number of instances.Related issue/s
How to test
Dev Checklist
DevOps Checklist