F #7334: Document OpenNebula allocation error handling#763
Merged
Conversation
Signed-off-by: Rostyslav Yatsyshyn <ryatsyshyn@opennebula.io>
tinova
approved these changes
Jul 14, 2026
mattrowe-opennebula
pushed a commit
that referenced
this pull request
Jul 20, 2026
Signed-off-by: Rostyslav Yatsyshyn <ryatsyshyn@opennebula.io>
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
2 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.
Description
Documents the fail-fast behavior introduced for OpenNebula Image and VM Template allocation failures.
OneSwap now reports the full OpenNebula API error and stops the current conversion instead of continuing with invalid object IDs or waiting for an Image that was not created.
Converted local disks remain available according to the existing failed-conversion cleanup behavior.
Branches to which this PR applies