Sudhansu Sahu created CLOUDSTACK-9831:
-----------------------------------------
Summary: Previous pod_id still remains in the vm_instance table
after VM migration with migrateVirtualMachineWithVolume
Key: CLOUDSTACK-9831
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9831
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.10.0.0
Reporter: Sudhansu Sahu
Previous pod_id still remains in the vm_instance table after VM migration with
migrateVirtualMachineWithVolume
{noformat}
Previous pod_id still remains in the vm_instance table after VM migration with
migrateVirtualMachineWithVolume
Before migrateVirtualMachineWithVolume
mysql> select v.id,v.instance_name,h.name,v.pod_id as
pod_id_from_instance_tb,h.pod_id as pod_id_from_host_tb from vm_instance v,
host h where v.host_id=h.id and v.id=2;
------------------------------------------------------------------------------------------------------
id instance_name name pod_id_from_instance_tb
pod_id_from_host_tb
------------------------------------------------------------------------------------------------------
2 i-2-2-VM testVM 1 1
------------------------------------------------------------------------------------------------------
1 row in set (0.00 sec)
After migrateVirtualMachineWithVolume
mysql> select v.id,v.instance_name,h.name,v.pod_id as
pod_id_from_instance_tb,h.pod_id as pod_id_from_host_tb from vm_instance v,
host h where v.host_id=h.id and v.id=3;
-----------------------------------------------------------------------------------------------------
id instance_name name pod_id_from_instance_tb
pod_id_from_host_tb
-----------------------------------------------------------------------------------------------------
3 i-2-3-VM testVm1 1 2
-----------------------------------------------------------------------------------------------------
1 row in set (0.00 sec)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
