[
https://issues.apache.org/jira/browse/CLOUDSTACK-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617174#comment-13617174
]
Prasanna Santhanam commented on CLOUDSTACK-1841:
------------------------------------------------
Did an upgrade from 4.0 to 4.1
In 4.0 DB:
mysql> select name,value from configuration where name like '%ipv6%';
Empty set (0.00 sec)
mysql> select name,value from configuration where name like '%traffic%';
Empty set (0.00 sec)
mysql> select name,value from configuration where name like '%snapshots%';
+-----------------------+-------+
| name | value |
+-----------------------+-------+
| max.account.snapshots | 20 |
| max.project.snapshots | 20 |
+-----------------------+-------+
2 rows in set (0.00 sec)
Upgrade:
INFO [utils.component.ComponentContext] (Timer-2:) Running
SystemIntegrityChecker encryptionSecretKeyChecker
INFO [utils.component.ComponentContext] (Timer-2:) Running
SystemIntegrityChecker databaseIntegrityChecker
INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to
check for database integrity.
INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database
integrity check
INFO [utils.component.ComponentContext] (Timer-2:) Running
SystemIntegrityChecker managementServerNode
INFO [utils.component.ComponentContext] (Timer-2:) Running
SystemIntegrityChecker databaseUpgradeChecker
INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to check
for database upgrade.
INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version =
4.0.0.2013-03-29T06:45:38Z Code Version = 4.1.0-SNAPSHOT
INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must
be performed from 4.0.0.2013-03-29T06:45:38Z to 4.1.0-SNAPSHOT
INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Cleaning upgrades
because all management server are now at the same version
INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Cleanup upgrade
Upgrade40to41 to upgrade from 4.0.0-4.1.0 to 4.1.0
In 4.1 DB:
mysql> select name,value from configuration where name like '%snapshots%';
+----------------------------------------+-------+
| name | value |
+----------------------------------------+-------+
| concurrent.snapshots.threshold.perhost | NULL |
| max.account.snapshots | 20 |
| max.project.snapshots | 20 |
+----------------------------------------+-------+
3 rows in set (0.00 sec)
mysql> select name,value from configuration where name like '%ipv6%';
+-------------------------------+-------+
| name | value |
+-------------------------------+-------+
| network.ipv6.search.retry.max | 10000 |
+-------------------------------+-------+
1 row in set (0.00 sec)
mysql> select name,value from configuration where name like '%traffic%';
+--------------------------------+----------+
| name | value |
+--------------------------------+----------+
| traffic.sentinel.exclude.zones | |
| traffic.sentinel.include.zones | EXTERNAL |
+--------------------------------+----------+
2 rows in set (0.00 sec)
> ASF 4.0 to 4.1 Upgrade: Missing Few Global Configuration parameters on the
> Upgraded Setup
> -----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1841
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1841
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Reporter: Chandan Purushothama
> Priority: Critical
> Fix For: 4.1.0
>
> Attachments: UICapture5.PNG
>
>
> ================
> Steps to Reproduce:
> ================
> 1. Upgrade ASF 4.0 setup to 4.1
> ==========
> Observations:
> ==========
> I attached the screenshot of missing parameters on the Upgraded Setup.
--
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
