Repository navigation
fix: avoid premature rescheduling when pool devices disappear - #75
Merged
shogom2 merged 1 commit intoSep 8, 2026
Merged
Conversation
Signed-off-by: Ko Kai <ko.kai@jp.fujitsu.com>
NekoHK
requested review from
KobayashiD27,
hase1128 and
shogom2
as code owners
September 8, 2026 08:33
shogom2
approved these changes
Sep 8, 2026
hase1128
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR prevents DDS from immediately setting
FabricDeviceFailedwhen an allocated device disappears from its pool ResourceSlice during attachment.It also resolves missing device models from the allocation pool so claims can proceed through the normal rescheduling checks.
Changes