ade
>>>> class will be initialized and ran before any other bean in
>>>> CloudStack is even initiated. So this works around all these DB
>>>> problems. The current spring setup in master is very, very
>>>> fragile. As I said before, it is re
an in CloudStack
>>>> is even initiated. So this works around all these DB problems. The
>>>> current spring setup in master is very, very fragile. As I said
>>>> before, it is really difficult to ensure certain aspects are
>>>> initialized before other
ng DB schema upgrades purely on startup of the mgmt
>>> server, we now have to be extra careful about initialization order.
>>>
>>> Darren
>>>
>>> On Tue, Oct 8, 2013 at 11:34 AM, Rayees Namathponnan
>>> wrote:
>>>> Here the defect created
server, we now have to be extra careful about initialization order.
>>
>> Darren
>>
>> On Tue, Oct 8, 2013 at 11:34 AM, Rayees Namathponnan
>> wrote:
>>> Here the defect created for this issue
>>>
>>> https://issues.apache.org/jira/browse/CLOUDSTACK-482
ue, Oct 8, 2013 at 11:34 AM, Rayees Namathponnan
> wrote:
>> Here the defect created for this issue
>>
>> https://issues.apache.org/jira/browse/CLOUDSTACK-4825
>>
>>
>> Regards,
>> Rayees
>>
>> -Original Message-
>> From: Franco
udrea...@cloudops.com]
> Sent: Tuesday, October 08, 2013 11:15 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Latest Master DB issue
>
> I guess in my case, it's fine. It was a fresh install...
>
> Francois
>
> On 10/8/2013, 2:08 PM, Darren Shepherd wrote:
>> Deploy db fr
Master DB issue
I guess in my case, it's fine. It was a fresh install...
Francois
On 10/8/2013, 2:08 PM, Darren Shepherd wrote:
> Deploy db from maven will drop all the tables. Not sure if this is
> fresh install or not. For master, running mvn will be your best bet.
> Otherwise y
I guess in my case, it's fine. It was a fresh install...
Francois
On 10/8/2013, 2:08 PM, Darren Shepherd wrote:
Deploy db from maven will drop all the tables. Not sure if this is
fresh install or not. For master, running mvn will be your best bet.
Otherwise you can look at running com.cloud.u
Deploy db from maven will drop all the tables. Not sure if this is
fresh install or not. For master, running mvn will be your best bet.
Otherwise you can look at running com.cloud.upgrade.DatabaseCreator
manually if your adventurous.
Darren
On Tue, Oct 8, 2013 at 10:55 AM, Francois Gaudreault
I'm not familiar with RPM install, but I don't think that the workaround
would be valid for everyone - QA folks will not have mvn install on their
machines, so this issue is a blocker for them. You can try it on your
setup though to unblock yourself.
It does have to be fixed in master, either by s
Thanks Alena for the explaination.
What is the better path to fix this on our setup? Should I wait for a
fix in master or should I manually run the deploydb with mvn? I guess
the second option won't work since I used RPM?
Francois
On 10/8/2013, 1:47 PM, Alena Prokharchyk wrote:
Ok, this is
Just throwing in a pitch for my spring-modularization branch. The DB
initialization stuff should all be fixed in the spring-modularization
branch. If it isn't we can better address it there anyhow. The
current initialization of spring in master is pure madness. When it
works, its because it jus
Ok, this is what going on - the DB upgrade procedure is different on
developer's setup and when deployed using cloudstack-setup-databases
On developers setup:
1) you deploy the code
2) Deploy the DB using 'mvn -P developer -pl developer -Ddeploydb'. As a
part of this step, the DataBaseUpgradeChec
Hmm... I just checked the DB version and it's 4.0??? It should be 4.3.0 no?
mysql> select * from version;
++-+-+--+
| id | version | updated | step |
++-+-+--+
| 1 | 4.0.0 | 2013-10-08 10:58:49 | Co
It's a fresh master RPM install.
Francois
On 10/8/2013, 12:40 PM, Alena Prokharchyk wrote:
It is not a small issue. is_default filed was added to the table as a part
of the 41-42 db upgrade. Looks like the code tries to retrieve system user
before the db upgrade is completed.
DB upgrade is a m
It is not a small issue. is_default filed was added to the table as a part
of the 41-42 db upgrade. Looks like the code tries to retrieve system user
before the db upgrade is completed.
DB upgrade is a major part of system integrity check; no queries to the DB
should be made before its completed.
16 matches
Mail list logo
