cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Animesh Chaturvedi <animesh.chaturv...@citrix.com>
Subject RE: There is no upgrade path from 4.1.1 to 4.2.0
Date Thu, 12 Sep 2013 01:11:01 GMT


From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Wednesday, September 11, 2013 5:54 PM
To: <dev@cloudstack.apache.org>; Animesh Chaturvedi
Subject: Re: There is no upgrade path from 4.1.1 to 4.2.0

Animesh,

I have not checked on this myself.

I believe that you have not yet promoted the bits from dist/dev to dist/release.  If that's
the case, we CAN fix this with a re-spin.  Not being able to upgrade from the 4.1.1 release
is a MAJOR ISSUE, since we had a security vulnerability announcement where we asked everyone
to upgrade to that bug-fix release.
[Animesh>] yes I have not promoted the bits yet, this needs to be taken care of.

I see that this thread has moved onto talking about the technical aspects of "why we do it
this way", but I want to make this point.  If we have not promoted the artifacts, we can fix
this!  If they are promoted, we're done with 4.2.0...  period, and no going back.  We can't
re-release with the same version number per ASF release policy.



On Wed, Sep 11, 2013 at 11:17 AM, Milamber <milamber@apache.org<mailto:milamber@apache.org>>
wrote:

Le 11/09/2013 15:42, Sudha Ponnaganti a ecrit :

This indicates to me that this is tested already

https://issues.apache.org/jira/browse/CLOUDSTACK-4509

In CS-4509, the management log file show two db upgrade:

2013-08-26 20:56:19,257 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version
= 4.0.0 Code Version = 4.1.0
2013-08-26 20:56:19,258 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database
upgrade must be performed from 4.0.0 to 4.1.0
2013-08-26 20:56:19,258 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Running
upgrade Upgrade40to41 to upgrade from 4.0.0-4.1.0 to 4.1.0


and

2013-08-26 22:08:43,111 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:null) DB version
= 4.1.0 Code Version = 4.2.0
2013-08-26 22:08:43,113 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:null) Database
upgrade must be performed from 4.1.0 to 4.2.0
2013-08-26 22:08:43,114 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:null) Running
upgrade Upgrade410to420 to upgrade from 4.1.0-4.2.0 to 4.2.0


Nothing from 4.1.1 to 4.2.0






-----Original Message-----
From: Wei ZHOU [mailto:ustcweizhou@gmail.com<mailto:ustcweizhou@gmail.com>]
Sent: Wednesday, September 11, 2013 7:37 AM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subject: Re: There is no upgrade path from 4.1.1 to 4.2.0

I do not find anything related in
./engine/schema/src/com/cloud/upgrade/DatabaseUpgradeChecker.java, and no Upgrade411to420.java
in ./engine/schema/src/com/cloud/upgrade/dao/ as well.
This should be a blocker issue.


2013/9/11 Milamber <milamber@apache.org<mailto:milamber@apache.org>>
Hello,

I've try to upgrade my CS test platform from 4.1.1 to 4.2.0 (from
Commit: e39a7d8e0d3f2fd3e326b1bdf4aaf9**ba5d900b02
+  CLVM issue cherry-pick from 4.2-forward with commitId
f2c5b5fbfe45196dfad2821fca513d**dd6efa25c9.)

The path 4.1.1->4.2.0 seems miss?

2013-09-11 14:32:55,619 INFO  [cloud.upgrade.**DatabaseUpgradeChecker]
(Timer-1:null) Grabbing lock to check for database upgrade.
2013-09-11 14:32:55,631 INFO  [cloud.upgrade.**DatabaseUpgradeChecker]
(Timer-1:null) DB version = 4.1.1 Code Version = 4.2.0
2013-09-11 14:32:55,632 INFO  [cloud.upgrade.**DatabaseUpgradeChecker]
(Timer-1:null) Database upgrade must be performed from 4.1.1 to 4.2.0
2013-09-11 14:32:55,632 ERROR [cloud.upgrade.**DatabaseUpgradeChecker]
(Timer-1:null) There is no upgrade path from 4.1.1 to 4.2.0
2013-09-11 14:32:55,639 ERROR [utils.component.**ComponentContext]
(Timer-1:null) System integrity check failed. Refuse to startup
com.cloud.utils.exception.**CloudRuntimeException: There is no upgrade
path from 4.1.1 to 4.2.0
     at com.cloud.upgrade.**DatabaseUpgradeChecker.**upgrade(**
DatabaseUpgradeChecker.java:**221)
     at com.cloud.upgrade.**DatabaseUpgradeChecker.check(**
DatabaseUpgradeChecker.java:**389)
     at com.cloud.utils.component.**ComponentContext.**
initComponentsLifeCycle(**ComponentContext.java:90)
     at com.cloud.servlet.**CloudStartupServlet$1.run(**
CloudStartupServlet.java:54)
     at java.util.TimerThread.**mainLoop(Timer.java:534)
     at java.util.TimerThread.run(**Timer.java:484)


Milamber



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message