You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Chandan Purushothama (JIRA)" <ji...@apache.org> on 2013/07/18 21:42:48 UTC
[jira] [Created] (CLOUDSTACK-3648) 3.0.6 to ASF 4.2 Upgrade:
"hypervisor_capabilites" table has duplicate VMware 5.1 entries on the
Upgraded Setup
Chandan Purushothama created CLOUDSTACK-3648:
------------------------------------------------
Summary: 3.0.6 to ASF 4.2 Upgrade: "hypervisor_capabilites" table has duplicate VMware 5.1 entries on the Upgraded Setup
Key: CLOUDSTACK-3648
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3648
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Upgrade
Affects Versions: 4.2.0
Reporter: Chandan Purushothama
Fix For: 4.2.0
mysql> select * from hypervisor_capabilities where hypervisor_version="5.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 |
+----+--------------------------------------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| 13 | 13 | VMware | 5.1 | 128 | 0 | 6 | 32 | 0 | 1 |
| 18 | 67648598-ed85-11e2-a76b-0649e40006c6 | VMware | 5.1 | 128 | 0 | 6 | 32 | 0 | 1 |
+----+--------------------------------------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
2 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