-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CLOUDSTACK-9831: Previous pod_id still remains in the vm_instance table #2002
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
Conversation
|
@sudhansu7 Shouldn't we update POD id upon a successful migration? If migration fails we will have wrong POD id in the DB. |
d3aac19 to
46b74ae
Compare
|
@serg38 |
|
LGTM on the code changes. |
|
LGTM on the code review. @borisstoyanov @rhtyd Can you kick off tests for this PR? |
|
@blueorangutan package |
|
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-607 |
|
@blueorangutan test |
|
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-971)
|
borisstoyanov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
marvin tests results and code changes LGTM
…le after VM migration with migrateVirtualMachineWithVolume
46b74ae to
3564d30
Compare
|
tag:mergeready |
|
@sudhansu7 can you change the base branch to 4.9 please, otherwise LGTM |
Previous pod_id still remains in the vm_instance table after VM migration with migrateVirtualMachineWithVolume