You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Kevin Kluge <Ke...@citrix.com> on 2012/04/23 17:57:17 UTC
RE: Code vs DB version
Moving over to the public mailing list.
Salvatore, which branch were you working on?
-kevin
From: Salvatore Orlando
Sent: Monday, April 23, 2012 8:34 AM
Subject: Code vs DB version
I had the following error while starting up the management server with fresh code and pre-existing db:
2012-04-23 08:12:12,220 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (main:null) The end upgrade version is actually at 3.0.3 but our management server code version is at 3.0.2.2012-04-23T15:03:57Z
2012-04-23 08:12:12,223 ERROR [utils.component.ComponentLocator] (main:null) Problems with running checker:DatabaseUpgradeChecker
com.cloud.utils.exception.CloudRuntimeException: The end upgrade version is actually at 3.0.3 but our management server code version is at 3.0.2.2012-04-23T15:03:57Z
It seems that build/cloud.properties needs to be updated accordingly, is that correct?
# major.minor.patch versioning scheme for CloudStack
company.major.version=3
company.minor.version=0
company.patch.version=2 <-- Should this be 3?
This problem does not happen to me on fresh installs (new DB). Seems specific to DB upgrade.
Please tell me if I'm doing something wrong
Thanks in advance,
Salvatore
RE: Code vs DB version
Posted by Frank Zhang <Fr...@citrix.com>.
done
-----Original Message-----
From: Alena Prokharchyk
Sent: Monday, April 23, 2012 9:57 AM
To: cloudstack-dev@incubator.apache.org; Kevin Kluge; Salvatore Orlando; Frank Zhang
Subject: RE: Code vs DB version
Frank,
Can you please change 3.0.x and master versions to be 3.0.3?
Thanks,
Alena.
-----Original Message-----
From: Salvatore Orlando [mailto:Salvatore.Orlando@eu.citrix.com]
Sent: Monday, April 23, 2012 9:10 AM
To: Kevin Kluge; cloudstack-dev@incubator.apache.org
Subject: RE: Code vs DB version
I was running the branch with the SDN controller (final test before check in master and 3.0.x), and I though the problem might be specific to that branch.
I then switched to master, but I am having the same problem.
I think we can exclude the problem being due to an incorrect db state, as it seems that the DatabaseUpgradeChecker looks at latest available upgrade class and at current code version, therefore not looking at the database at all.
Changing the patch version to '3' solves this problem, apparently.
Salvatore
From: Kevin Kluge
Sent: 23 April 2012 16:57
To: Salvatore Orlando; cloudstack-dev@incubator.apache.org
Subject: RE: Code vs DB version
Moving over to the public mailing list.
Salvatore, which branch were you working on?
-kevin
From: Salvatore Orlando
Sent: Monday, April 23, 2012 8:34 AM
Subject: Code vs DB version
I had the following error while starting up the management server with fresh code and pre-existing db:
2012-04-23 08:12:12,220 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (main:null) The end upgrade version is actually at 3.0.3 but our management server code version is at 3.0.2.2012-04-23T15:03:57Z
2012-04-23 08:12:12,223 ERROR [utils.component.ComponentLocator] (main:null) Problems with running checker:DatabaseUpgradeChecker
com.cloud.utils.exception.CloudRuntimeException: The end upgrade version is actually at 3.0.3 but our management server code version is at 3.0.2.2012-04-23T15:03:57Z
It seems that build/cloud.properties needs to be updated accordingly, is that correct?
# major.minor.patch versioning scheme for CloudStack
company.major.version=3
company.minor.version=0
company.patch.version=2 <-- Should this be 3?
This problem does not happen to me on fresh installs (new DB). Seems specific to DB upgrade.
Please tell me if I'm doing something wrong
Thanks in advance,
Salvatore
RE: Code vs DB version
Posted by Alena Prokharchyk <Al...@citrix.com>.
Frank,
Can you please change 3.0.x and master versions to be 3.0.3?
Thanks,
Alena.
-----Original Message-----
From: Salvatore Orlando [mailto:Salvatore.Orlando@eu.citrix.com]
Sent: Monday, April 23, 2012 9:10 AM
To: Kevin Kluge; cloudstack-dev@incubator.apache.org
Subject: RE: Code vs DB version
I was running the branch with the SDN controller (final test before check in master and 3.0.x), and I though the problem might be specific to that branch.
I then switched to master, but I am having the same problem.
I think we can exclude the problem being due to an incorrect db state, as it seems that the DatabaseUpgradeChecker looks at latest available upgrade class and at current code version, therefore not looking at the database at all.
Changing the patch version to '3' solves this problem, apparently.
Salvatore
From: Kevin Kluge
Sent: 23 April 2012 16:57
To: Salvatore Orlando; cloudstack-dev@incubator.apache.org
Subject: RE: Code vs DB version
Moving over to the public mailing list.
Salvatore, which branch were you working on?
-kevin
From: Salvatore Orlando
Sent: Monday, April 23, 2012 8:34 AM
Subject: Code vs DB version
I had the following error while starting up the management server with fresh code and pre-existing db:
2012-04-23 08:12:12,220 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (main:null) The end upgrade version is actually at 3.0.3 but our management server code version is at 3.0.2.2012-04-23T15:03:57Z
2012-04-23 08:12:12,223 ERROR [utils.component.ComponentLocator] (main:null) Problems with running checker:DatabaseUpgradeChecker
com.cloud.utils.exception.CloudRuntimeException: The end upgrade version is actually at 3.0.3 but our management server code version is at 3.0.2.2012-04-23T15:03:57Z
It seems that build/cloud.properties needs to be updated accordingly, is that correct?
# major.minor.patch versioning scheme for CloudStack
company.major.version=3
company.minor.version=0
company.patch.version=2 <-- Should this be 3?
This problem does not happen to me on fresh installs (new DB). Seems specific to DB upgrade.
Please tell me if I'm doing something wrong
Thanks in advance,
Salvatore
RE: Code vs DB version
Posted by Salvatore Orlando <Sa...@eu.citrix.com>.
I was running the branch with the SDN controller (final test before check in master and 3.0.x), and I though the problem might be specific to that branch.
I then switched to master, but I am having the same problem.
I think we can exclude the problem being due to an incorrect db state, as it seems that the DatabaseUpgradeChecker looks at latest available upgrade class and at current code version, therefore not looking at the database at all.
Changing the patch version to '3' solves this problem, apparently.
Salvatore
From: Kevin Kluge
Sent: 23 April 2012 16:57
To: Salvatore Orlando; cloudstack-dev@incubator.apache.org
Subject: RE: Code vs DB version
Moving over to the public mailing list.
Salvatore, which branch were you working on?
-kevin
From: Salvatore Orlando
Sent: Monday, April 23, 2012 8:34 AM
Subject: Code vs DB version
I had the following error while starting up the management server with fresh code and pre-existing db:
2012-04-23 08:12:12,220 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (main:null) The end upgrade version is actually at 3.0.3 but our management server code version is at 3.0.2.2012-04-23T15:03:57Z
2012-04-23 08:12:12,223 ERROR [utils.component.ComponentLocator] (main:null) Problems with running checker:DatabaseUpgradeChecker
com.cloud.utils.exception.CloudRuntimeException: The end upgrade version is actually at 3.0.3 but our management server code version is at 3.0.2.2012-04-23T15:03:57Z
It seems that build/cloud.properties needs to be updated accordingly, is that correct?
# major.minor.patch versioning scheme for CloudStack
company.major.version=3
company.minor.version=0
company.patch.version=2 <-- Should this be 3?
This problem does not happen to me on fresh installs (new DB). Seems specific to DB upgrade.
Please tell me if I'm doing something wrong
Thanks in advance,
Salvatore