[ovirt] fix issues with oVirt 3.1 API. #1591
Merged
Conversation
This file contains 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
ohadlevy
added a commit
that referenced
this pull request
Feb 25, 2013
[ovirt] fix issues with oVirt 3.1 API disk locking status.
|
@abenari thanks! |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In version 3.1 of oVirt API there is a change in the meaning of the virtual machine (VM) status. When creating a VM in versions prior to 3.1, it used to be in status 'image-locked' until the virtual disks where ready. In version 3.1 a change in the API was introduced, the VM status no longer represent the status of the VM and it's disks, from this version, in order to know that a VM is ready for launch, we need to loop through the disks checking the state of each one.
This patch fix the oVirt launch logic, it is backward compatible with previous oVirt versions.