Skip to content
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

Windows nodes not removed after termination #9

Closed
caneridge opened this issue Oct 4, 2017 · 1 comment
Closed

Windows nodes not removed after termination #9

caneridge opened this issue Oct 4, 2017 · 1 comment
Labels

Comments

@caneridge
Copy link

I started a spot fleet in AWS. The bidding went up to $15/hr for several hours. My max bid price was $1.50. All of the instances for my spot instance were terminated by AWS. In Jenkins, I had about 2 dozen dead instances that Jenkins failed to remove. I was able to remove the instances manually one at a time in Jenkins. Deleting the fleet configuration in Jenkins and restarting also removes the instances. The bug is that this plugin does not gracefully handle the case where AWS cancels all of the instances for the spot fleet and is unable to provision additional instances. The instances are marked as down in Jenkins and are not removed. This is currently happening for c3.2xlarge Windows which has been completely sold out for several hours in AWS today. It was not even possible to start an on-demand instance.

@terma
Copy link

terma commented May 21, 2019

Thx for report, fix was released under 1.1.8, feel free to reopen if any questions

@terma terma closed this as completed May 21, 2019
@terma terma added the bug label May 21, 2019
terma pushed a commit that referenced this issue Sep 8, 2019
Many new features and bugfixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants