cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4165) 3.0.6 to ASF 4.2 Upgrade: Data Migration step of the Upgrade Fails on "persistLegacyZones"
Date Thu, 08 Aug 2013 09:02:50 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733278#comment-13733278
] 

ASF subversion and git services commented on CLOUDSTACK-4165:
-------------------------------------------------------------

Commit 3e85f480c429ef8f08f64f02f80f4f8626f8353a in branch refs/heads/master from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3e85f48 ]

CLOUDSTACK-4165 3.0.6 to ASF 4.2 Upgrade: Data Migration step of the Upgrade Fails on "persistLegacyZones"

Track the Datacenter of previous cluster correctly while going through each cluster in the
zone to see if 2 clusters are from different DC/vCenter.

Cherry picked from 4.2 commit a3450afff558d1d04a7dd4697f4d152f3a0aba33

Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>

                
> 3.0.6 to ASF 4.2 Upgrade: Data Migration step of the Upgrade Fails on "persistLegacyZones"
> ------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4165
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4165
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Chandan Purushothama
>            Assignee: Sateesh Chodapuneedi
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: management-server.zip, mysqldumps.zip
>
>
> =================
> Steps to Reproduce:
> =================
> 1. Deployed a 3.0.6 Advanced Zone Setup with two VMWare Clusters with one host in each
Cluster. Used NFS Primary Storage.
> 2. Upgraded the Setup using the Latest 4.2 Build.
> ===========
> Observations:
> ===========
> On Starting the Management Server after Upgrading the RPMs, I observed that the schema
of the setup got upgraded but failed before data migration phase started.
> =======================
> On Management Server Log:
> =======================
> 2013-08-07 14:10:57,271 DEBUG [utils.db.ScriptRunner] (Timer-1:null) INSERT IGNORE INTO
`cloud`.`configuration` VALUES ('Advanced', 'DEFAULT', 'management-server', 'eip.use.multiple.netscalers',
'false', 'Should be set to true, if there will be multiple NetScaler devices providing EIP
service in a zone')
> 2013-08-07 14:10:57,272 DEBUG [utils.db.ScriptRunner] (Timer-1:null) INSERT IGNORE INTO
`cloud`.`configuration` VALUES ('Snapshots', 'DEFAULT', 'SnapshotManager', 'snapshot.backup.rightafter',
'true', 'backup snapshot right after snapshot is taken')
> 2013-08-07 14:10:57,363 TRACE [db.Transaction.Connection] (Timer-1:null) txn: Not closing
DB connection because we're still in a transaction.
> 2013-08-07 14:10:57,364 DEBUG [db.Transaction.Transaction] (Timer-1:null) Rolling back
the transaction: Time = 5301 Name =  -CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484;
called by -Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
> 2013-08-07 14:10:57,365 TRACE [db.Transaction.Connection] (Timer-1:null) Closing DB connection:
dbconn162979043
> 2013-08-07 14:10:57,366 TRACE [utils.db.GlobalLock] (Timer-1:null) lock DatabaseUpgrade
is returned to free state, total holding time :8969
> 2013-08-07 14:10:57,366 TRACE [utils.db.GlobalLock] (Timer-1:null) lock DatabaseUpgrade
is released, lock count :0
> 2013-08-07 14:10:57,366 ERROR [utils.component.ComponentContext] (Timer-1:null) System
integrity check failed. Refuse to startup

--
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

Mime
View raw message