Srikanteswararao Talluri created CLOUDSTACK-4079:
----------------------------------------------------
Summary: UPGRADE: storage_motion_supported field is not updated
for xenserver6.1 in hypervisor_capabilities table after upgrade
Key: CLOUDSTACK-4079
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4079
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Upgrade
Affects Versions: 4.2.0
Environment: xenserver
Reporter: Srikanteswararao Talluri
Priority: Blocker
Fix For: 4.2.0
storage_motion_supported field is not updated for xenserver6.1 in
hypervisor_capabilities table after upgrade
This is observed on the following upgraded setups:
3.0.7 -> 4.2
3.0.5 -> 4.2
mysql> select * from hypervisor_capabilities;
+----+--------------------------------------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| id | uuid | hypervisor_type |
hypervisor_version | max_guests_limit | security_group_enabled |
max_data_volumes_limit | max_hosts_per_cluster | storage_motion_supported |
vm_snapshot_enabled |
+----+--------------------------------------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| 1 | 1 | XenServer | default
| 50 | 1 | 6 |
NULL | 0 | 1 |
| 2 | 2 | XenServer | XCP 1.0
| 50 | 1 | 6 |
NULL | 0 | 1 |
| 3 | 3 | XenServer | 5.6
| 50 | 1 | 6 |
NULL | 0 | 1 |
| 4 | 4 | XenServer | 5.6 FP1
| 50 | 1 | 6 |
NULL | 0 | 1 |
| 5 | 5 | XenServer | 5.6 SP2
| 50 | 1 | 6 |
NULL | 0 | 1 |
| 6 | 6 | XenServer | 6.0
| 50 | 1 | 13 |
NULL | 0 | 1 |
| 7 | 7 | XenServer | 6.0.2
| 50 | 1 | 13 |
NULL | 0 | 1 |
| 8 | 8 | XenServer | 6.1.0
| 50 | 1 | 13 |
NULL | 0 | 1 |
| 9 | 9 | VMware | default
| 128 | 0 | 6 |
32 | 0 | 1 |
| 10 | 10 | VMware | 4.0
| 128 | 0 | 6 |
32 | 0 | 1 |
| 11 | 11 | VMware | 4.1
| 128 | 0 | 6 |
32 | 0 | 1 |
| 12 | 12 | VMware | 5.0
| 128 | 0 | 6 |
32 | 1 | 1 |
| 13 | 13 | VMware | 5.1
| 128 | 0 | 6 |
32 | 1 | 1 |
| 14 | 14 | KVM | default
| 50 | 1 | 6 |
NULL | 0 | 0 |
| 15 | 15 | Ovm | default
| 25 | 1 | 6 |
NULL | 0 | 0 |
| 16 | 16 | Ovm | 2.3
| 25 | 1 | 6 |
NULL | 0 | 0 |
| 18 | f721ea58-fdee-11e2-975c-066d9a000069 | XenServer | 6.2.0
| 50 | 1 | 13 |
NULL | 1 | 1 |
| 20 | f867f768-fdee-11e2-975c-066d9a000069 | LXC | default
| 50 | 1 | 6 |
NULL | 0 | 0 |
+----+--------------------------------------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
18 rows in set (0.01 sec)
mysql> select * from hypervisor_capabilities where storage_motion_supported=1;
+----+--------------------------------------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| id | uuid | hypervisor_type |
hypervisor_version | max_guests_limit | security_group_enabled |
max_data_volumes_limit | max_hosts_per_cluster | storage_motion_supported |
vm_snapshot_enabled |
+----+--------------------------------------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| 12 | 12 | VMware | 5.0
| 128 | 0 | 6 |
32 | 1 | 1 |
| 13 | 13 | VMware | 5.1
| 128 | 0 | 6 |
32 | 1 | 1 |
| 18 | f721ea58-fdee-11e2-975c-066d9a000069 | XenServer | 6.2.0
| 50 | 1 | 13 |
NULL | 1 | 1 |
+----+--------------------------------------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
3 rows in set (0.00 sec)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
