Skip to content

nodedisruption: reject instead of pending when preparing past deadline#90

Merged
damsallem merged 1 commit into
criteo:mainfrom
damsallem:main
Jul 23, 2026
Merged

nodedisruption: reject instead of pending when preparing past deadline#90
damsallem merged 1 commit into
criteo:mainfrom
damsallem:main

Conversation

@damsallem

Copy link
Copy Markdown
Contributor
  • When an app was in "preparing" state and the retryable ND reach the deadline, we would never call the next step to the app since deadline is reached (setting "AnyFailed" at true).
  • It was making the ND to be never deleted, because it would never reached a final state (granted or rejected).
  • Here the goals is to force reject (like before the revamp of the API) if the deadline is reached.
  • NB: /terminate is out of the state-machine, so it will be called at deletion of the ND, even if the deadline is reached !

* When an app was in "preparing" state and the retryable ND reach the deadline,
we would never call the next step to the app since deadline is reached
(setting "AnyFailed" at true).
* It was making the ND to be never deleted, because it would never
reached a final state (granted or rejected).
* Here the goals is to force reject (like before the revamp of the API)
if the deadline is reached.
* NB: /terminate is out of the state-machine, so it will be called at
deletion of the ND, even if the deadline is reached !

@itoumlilt itoumlilt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@damsallem
damsallem merged commit 492c943 into criteo:main Jul 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants