Sent: Friday, August 13, 2021 04:17
To: dev@cloudstack.apache.org
Subject: Error while database upgrade.
engine/schema/src/main/resources/META-INF/db/schema-41510to41600.sql
line:23
ALTER TABLE `cloud`.`service_offering` ADD COLUMN `dynamic_scaling_enabled`
tinyint(1) unsigned NOT NULL DEFA
engine/schema/src/main/resources/META-INF/db/schema-41510to41600.sql
line:23
ALTER TABLE `cloud`.`service_offering` ADD COLUMN `dynamic_scaling_enabled`
tinyint(1) unsigned NOT NULL DEFAULT 1 COMMENT 'true(1) if VM needs to be
dynamically scalable of cpu or memory';
Log message ...
ERROR [c.
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1665
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
Thanks @milamberspace
Based on the tests and LGTMs, I'll proceed with merging this on 4.9. On
fwd-merging, I've fixed conflicts and renamed a subsequent class to match the
change. Fwd-merged
chema upgrade from 4.9.0 to 4.9.1;"
Logs:
2016-09-02 15:13:45,721 INFO [c.c.u.DatabaseUpgradeChecker] (main:null)
(logid:) DB version = 4.9.0 Code Version = 4.9.1.0
2016-09-02 15:13:45,722 INFO [c.c.u.DatabaseUpgradeChecker] (main:null)
(logid:) Database upgrade must be perf
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
Tests performed after fwd-merge, all pass:
- Upgraded from 4.9.1.0
- Clean db deployment
---
If your project is set up for it, you can reply to this email and have your
reply
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
Tests performed:
- Upgraded from 4.9.0, upgrade path ran (whose sql file names were
changed)
- Clean db deployment
---
If your project is set up for it, you can reply to this
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fea
Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1665
@rhtyd good catch -- sorry for that oversight. I have redone the PR to
only rename the files and class.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
@jburwell we'll need that upgrade path class, we have some alter table
changes we want for the 4.9.0->4.9.1.0 upgrade path, see the diff for changes
you've removed.
---
If your project is set up
Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1665
@rhtyd I have fixed the ``DatabaseUpgradeCheckerTest`` to reflect 4.9.1.0
being a ``NoopUpgrade``. I also removed the unnecessary 4.9.0->4.9.1.0 upgrade
scripts and class.
---
If your projec
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
@jburwell this needs to be reworked now that #1654 is merged. Good to have
the changes but not a blocker for 4.8, 4.9 RCs.
---
If your project is set up for it, you can reply to this email and ha
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
With new db schema/versioning and upgrade changes in #1654 we can merge
this with some additional changes once #1654 is merged and fwd-merged.
---
If your project is set up for it, you can reply
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
@jburwell -1
The db upgrade version only considers the major/minor fields such as a.b.c,
the last `.d` is ignored (for that matter any other suffix in the version). Due
to the current mechanis
GitHub user jburwell opened a pull request:
https://github.com/apache/cloudstack/pull/1665
Changes database upgrade script names consistent for the 4.9.1.0 release
* Changes the names of the schema-490to491* scripts to
schema-490to4910*
* Changes the name of the
I gave it a quick shot. A test build is running and I'll create the pr in a
minute.
On Fri, Dec 4, 2015 at 9:51 AM, Rohit Yadav
wrote:
> Hi Daan, I’m testing quota but can work on it in 1-2 hours. So, not
> started yet but if you got time go ahead, and later I can help review/merge
> your PR.
>
Hi Daan, I’m testing quota but can work on it in 1-2 hours. So, not started yet
but if you got time go ahead, and later I can help review/merge your PR.
Regards.
On 04-Dec-2015, at 2:15 PM, Daan Hoogland
mailto:daan.hoogl...@gmail.com>> wrote:
Rohit, First of all good catch. I think we need to
Rohit, First of all good catch. I think we need to remove the 460to470 step
and have the path always pass by 4.6.1. Are you busy with this change
already?
On Fri, Dec 4, 2015 at 6:03 AM, Rohit Yadav
wrote:
> There seems to be a db view related change between 4.6.0 and 4.6.1 (DB)
> versions; and
There seems to be a db view related change between 4.6.0 and 4.6.1 (DB)
versions; and there exists separate DB upgrade paths from 4.6.0 to 4.7.0 and
4.6.1 to 4.7.0 on master branch which shares the same changes. The issue is
that the upgrade path from 4.6.0 to 4.7.0 does not include the db view
cker
> > 2013-09-24 02:23:48,145 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> > (Timer-1:null) Grabbing lock to check for database upgrade.
> > 2013-09-24 02:23:48,147 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null)
> > Checking to see if the database is at a version befo
l) Running SystemIntegrityChecker databaseUpgradeChecker
> 2013-09-24 02:23:48,145 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) Grabbing lock to check for database upgrade.
> 2013-09-24 02:23:48,147 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null)
> Checking to see if the database is at a
check for database upgrade.
2013-09-24 02:23:48,147 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null)
Checking to see if the database is at a version before it was the version
table is created
2013-09-24 02:23:48,154 INFO [cloud.upgrade.DatabaseUpgradeChecker]
(Timer-1:null) DB version = 4.1.1 Code
I did a submission, https://reviews.apache.org/r/13317/
On Mon, Aug 5, 2013 at 8:27 PM, Chip Childers wrote:
> On Mon, Aug 05, 2013 at 08:23:48PM +0200, Daan Hoogland wrote:
>> :) meaning now, i suppose.
>>
>> On Mon, Aug 5, 2013 at 7:12 PM, Chip Childers
>> wrote:
>> > On Mon, Aug 05, 2013 at
On Mon, Aug 05, 2013 at 08:23:48PM +0200, Daan Hoogland wrote:
> :) meaning now, i suppose.
>
> On Mon, Aug 5, 2013 at 7:12 PM, Chip Childers
> wrote:
> > On Mon, Aug 05, 2013 at 12:32:19PM +0200, Daan Hoogland wrote:
> >> H,
> >>
> >> What is the policy for adding upgrade paths?
> >>
> >> I am
:) meaning now, i suppose.
On Mon, Aug 5, 2013 at 7:12 PM, Chip Childers wrote:
> On Mon, Aug 05, 2013 at 12:32:19PM +0200, Daan Hoogland wrote:
>> H,
>>
>> What is the policy for adding upgrade paths?
>>
>> I am working on upgrade from 4.1.1 already.
>> So when do we add
>> _upgradeMap.p
On Mon, Aug 05, 2013 at 12:32:19PM +0200, Daan Hoogland wrote:
> H,
>
> What is the policy for adding upgrade paths?
>
> I am working on upgrade from 4.1.1 already.
> So when do we add
> _upgradeMap.put("4.1.1", new DbUpgrade[] { new
> Upgrade410to420(), new Upgrade420to430() });
> to Dat
H,
What is the policy for adding upgrade paths?
I am working on upgrade from 4.1.1 already.
So when do we add
_upgradeMap.put("4.1.1", new DbUpgrade[] { new
Upgrade410to420(), new Upgrade420to430() });
to DatabaseUpgradeChecker?
thanks,
Daan
/heads/master
from Chip Childers
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=099677a ]
CLOUDSTACK-2172: adding database upgrade to 4.1.0 in
PremiumDatabaseUpgradeChecker
Add migration to 4.1.0 in the PremiumDatabaseUpgradeChecker, like in the
DatabaseUpgradeChecker.
I opened the
/heads/4.1 from
Chip Childers
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=41e6e9f ]
CLOUDSTACK-2172: adding database upgrade to 4.1.0 in
PremiumDatabaseUpgradeChecker
Add migration to 4.1.0 in the PremiumDatabaseUpgradeChecker, like in the
DatabaseUpgradeChecker.
I opened the
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/10773/
---
(Updated April 25, 2013, 2:14 p.m.)
Review request for cloudstack.
Descriptio
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/10773/
---
Review request for cloudstack.
Description
---
Add migration to 4.1.0 in t
31 matches
Mail list logo
