Skip to content
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

fix for bug #4593 #104

Merged
merged 1 commit into from
Jun 23, 2016
Merged

fix for bug #4593 #104

merged 1 commit into from
Jun 23, 2016

Conversation

atodorov-storpool
Copy link
Contributor

Hi Developers,
http://dev.opennebula.org/issues/4593
When VM in UNKNOWN state is rescheduled it can not be migrated anymore because a check in VirtualMachineMigrate::request_execute is not satisfied due to previous history record not closed properly.
https://github.com/OpenNebula/one/blob/master/src/rm/RequestManagerVirtualMachine.cc#L1097

The suggested patch updates(closes) previous history record properly (I hope) and the VM is in proper state then.

Kind Regards,
Anton Todorov

Hi Developers,
http://dev.opennebula.org/issues/4593
When VM in UNKNOWN state is rescheduled it can not be migrated anymore because a check in VirtualMachineMigrate::request_execute is not satisfied due to previous history record not closed properly.
https://github.com/OpenNebula/one/blob/master/src/rm/RequestManagerVirtualMachine.cc#L1097

The suggested patch updates(closes) previous history record properly (I hope) and the VM is in proper state then.

Kind Regards,
Anton Todorov
@rsmontero rsmontero merged commit 58d7256 into OpenNebula:master Jun 23, 2016
@rsmontero
Copy link
Member

Needs to handle the other PROLOG_MIGRATE states and failure.

@rsmontero
Copy link
Member

Hi Anton,

After reviewing this, I've decided to move your changes to the action. This case is slightly different to the others as the capacity is decremented before issuing the prolog. So I prefer to treat the history record in a similar way to a POWEROFF/SUSPEND migration, where the actual registry is closed. All changes are now in master if you want to give them a try, but I basically moved the update from the callback to the trigger.

THANKS!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants