CA-413899: Rescan LVs whilst activating #778
Merged
Conversation
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
There is a small window where, if a VM is leaf coalesced whilst it is shutdown, that a subsequent atempt to activate the VDI will fail with `SR_BACKEND_FAILURE_46 (The VDI is not available)`. This appears to be due to the GC process not issuing a `_updateSlavesOnRename` request because the VDI is not active. To avoid this ensure that the `--refresh` is performed when attempting to attach/activate. Signed-off-by: Mark Syms <mark.syms@cloud.com>
TimSmithCtx
approved these changes
Oct 6, 2025
LunfanZhang
approved these changes
Nov 14, 2025
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.
There is a small window where, if a VM is leaf coalesced whilst it is shutdown, that a subsequent atempt to activate the VDI will fail with
SR_BACKEND_FAILURE_46 (The VDI is not available). This appears to be due to the GC process not issuing a_updateSlavesOnRenamerequest because the VDI is not active. To avoid this ensure that the--refreshis performed when attempting to attach/activate.