-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(vCenter) wait poweron/off to be performed #2262
Milestone
Comments
joseangelgm
added a commit
to joseangelgm/one
that referenced
this issue
Jul 23, 2018
joseangelgm
added a commit
to joseangelgm/one
that referenced
this issue
Jul 23, 2018
tinova
pushed a commit
that referenced
this issue
Jul 23, 2018
tinova
pushed a commit
that referenced
this issue
Jul 23, 2018
joseangelgm
added a commit
to joseangelgm/one
that referenced
this issue
Jul 23, 2018
joseangelgm
added a commit
to joseangelgm/one
that referenced
this issue
Jul 23, 2018
joseangelgm
added a commit
to joseangelgm/one
that referenced
this issue
Jul 23, 2018
tinova
pushed a commit
that referenced
this issue
Jul 23, 2018
rsmontero
pushed a commit
that referenced
this issue
Aug 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
vCenter Virtualization Driver (VMM) has an asyn behaviour considering poweron and poweroff actions.
This provoke certain failures.
To Reproduce
Start a vCenter VM -> vCenter driver (deploy operation) finishes, OpenNebula believe that the machine is already running but the fact is that is in the starting state -> turn off the machine before OpenNebula realizes the correct state.
Expected behavior
poweron and poweroff driver operations should be blocking, in that way opennebula could wait and set the proper state.
Details
The text was updated successfully, but these errors were encountered: