Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Decommission node strategy should delete nodes #2587

Closed
tevoinea opened this issue Oct 31, 2022 · 0 comments · Fixed by #2586
Closed

Decommission node strategy should delete nodes #2587

tevoinea opened this issue Oct 31, 2022 · 0 comments · Fixed by #2586
Assignees
@tevoinea
Labels
bug Something isn't working

Comments

@tevoinea
Copy link
Member

tevoinea commented Oct 31, 2022 •
edited by mgreisen
Loading

Information

  • Onefuzz version: 5.18.0
  • OS: N/A

Provide detailed reproduction steps (if any)

  1. Enable decommission node strategy
  2. Load up a scaleset with jobs such that it cannot auto scale up anymore

Expected result

What is the expected result of the above steps?

As nodes complete their work, they should release protection (this happens) then get reaped by auto scale.

Actual result

What is the actual result of the above steps?

Auto scale will not reap the nodes because there's still work pending in the pool queue so the system is stuck.

AB#42032276
@tevoinea tevoinea added the bug Something isn't working label Oct 31, 2022
@ghost ghost added the Needs: triage label Oct 31, 2022
@tevoinea tevoinea linked a pull request Oct 31, 2022 that will close this issue
Delete nodes on decommission instead of just releasing scale in protection #2586
Merged
@tevoinea tevoinea self-assigned this Oct 31, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Dec 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tevoinea tevoinea

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Delete nodes on decommission instead of just releasing scale in protection tevoinea/onefuzz
1 participant
@tevoinea