Chandan Purushothama created CLOUDSTACK-363:
-----------------------------------------------
Summary: Ugrades from 2.2.14, 3.0.2 to the Current build will fail
Key: CLOUDSTACK-363
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-363
Project: CloudStack
Issue Type: Bug
Components: Management Server
Affects Versions: pre-4.0.0
Reporter: Chandan Purushothama
Priority: Blocker
Fix For: pre-4.0.0
I see that the Version Information in the databases of the latest builds have a
timestamp as show below:
mysql> select * from mshost;
+----+-----------------+---------------+-------------+-------+--------------------+--------------+--------------+---------------------+---------+-------------+
| id | msid | runid | name | state | version
| service_ip | service_port | last_update | removed | alert_count |
+----+-----------------+---------------+-------------+-------+--------------------+--------------+--------------+---------------------+---------+-------------+
| 1 | 206915885077153 | 1350408417554 | Rack3Host11 | Up |
2.2.20121012230921 | 10.223.58.66 | 9090 | 2012-10-16 21:03:25 | NULL
| 0 |
+----+-----------------+---------------+-------------+-------+--------------------+--------------+--------------+---------------------+---------+-------------+
1 row in set (0.00 sec)
mysql> select * from version;
+----+--------------------+---------------------+----------+
| id | version | updated | step |
+----+--------------------+---------------------+----------+
| 1 | 2.2.20121012230921 | 2012-10-13 17:38:58 | Complete |
+----+--------------------+---------------------+----------+
1 row in set (0.00 sec)
This will break upgrades from 2.2.14 and 3.0.2 Builds to the Current Build
--
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
