I've done my best to test various DB upgrade scenarios and I believe
all this stuff should be fixed in the spring-modularization branch. I
stated wrong before, the database upgrade stuff is in the system
context. So the majority of ACS is in the "core" context which is
initialized after system.
Let me look at this today. The spring changes I have will greatly improve
these initialization issues. The current state of spring on master makes it
very difficult to deterministic ally initialize beans. With the spring changes
I have in place the database upgrade stuff is in the bootstrap c
It's fixed with commit 3f583684c6ddcf7efb66adada63957f8ca06cfdc
Not really the nicest of fixes, but at least the QA can continue. For a
structural fix we would need to run the database upgrade check before
initialising any of the beans. That can't be done yet as the upgrade checker
depends on a
Just pushed a stop-gap fix to master. I'm running my qa tests now to check if
it is ok now.
Cheers,
Hugo
Sent from my iPhone
> On 3 okt. 2013, at 12:18, Prasanna Santhanam wrote:
>
> This was my problem too for running tests o master :(
>
> I posted CLOUDSTACK-4791 today for the issue.
>
>
This was my problem too for running tests o master :(
I posted CLOUDSTACK-4791 today for the issue.
On Thu, Oct 03, 2013 at 11:08:16AM +0200, Hugo Trippaers wrote:
> Heya guys,
>
> I'm still running into this problem. Our jenkins automagically installs and
> tests the latest packages based on
Heya guys,
I'm still running into this problem. Our jenkins automagically installs and
tests the latest packages based on master. With a clean database on clean
machines.
The error reported is similar to the error encountered:
Caused by: com.cloud.utils.exception.CloudRuntimeException: DB Exce
works in the latest version
On Tue, Sep 24, 2013 at 4:09 PM, Daan Hoogland wrote:
> I ran into this as well, As I did some change to schema-420-430.sql I
> was my primary suspect. It does not have to do with my field though.
> Still looking,
> Daan
>
> On Tue, Sep 24, 2013 at 2:17 PM, Wei ZHOU w
I ran into this as well, As I did some change to schema-420-430.sql I
was my primary suspect. It does not have to do with my field though.
Still looking,
Daan
On Tue, Sep 24, 2013 at 2:17 PM, Wei ZHOU wrote:
> I ran a fresh installation on devcloud just now, it works.
> some records in configurat
I ran a fresh installation on devcloud just now, it works.
some records in configuration table are introduced by sql files, and
ConfigurationServerImpl will check and insert the records if not exist.
2013/9/24 Hugo Trippaers
> Hey all,
>
> Noticed an interesting problem today. I was trying to s
