On 20.01.2014 09:19, Harikrishna Patnala wrote:
Hi Nux,
Can you close the ticket if it was SNAPSHOTs issue, or you could try
with clean right 4.2.1, set it up and try upgrade.
Closed, cheers!
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Hi Nux,
Can you close the ticket if it was SNAPSHOTs issue, or you could try with clean
right 4.2.1, set it up and try upgrade.
Thanks
Harikrishna
On 19-Jan-2014, at 10:52 pm, Nux! wrote:
> On 19.01.2014 15:41, Marcus Sorensen wrote:
>> If it helps at all, in the past when i've run into this
On 19.01.2014 15:41, Marcus Sorensen wrote:
If it helps at all, in the past when i've run into this I've edited
the script to comment out the line that errored, and everything prior
to it, then restarted the mgmt server so it could pick up the upgrade
where it left off. It sometimes takes 2-3 tim
If it helps at all, in the past when i've run into this I've edited
the script to comment out the line that errored, and everything prior
to it, then restarted the mgmt server so it could pick up the upgrade
where it left off. It sometimes takes 2-3 times, but you essentially
just skip over whateve
Yes, there's no support for upgrading between dev builds, as the
schema is changing often. Devs start fresh with the current db schema
as they work on features. Upgrade scripts are only created between
release schemas.
On Sun, Jan 19, 2014 at 7:25 AM, Daan Hoogland wrote:
> Lucian,
>
> I read you
Lucian,
I read your ticket and think that playing with a snapshot is the
problem most likely. To be sure you might want to setup your env
(including vms) on a clean 4.2.1 and see if it happens then. The db
upgrade scheme we use is not repeatable and on a snapshot you might
have missed or gotten st
Hi,
DB upgrade fails from 4.2.1 to 4.3 on my setup. More info/logs here:
https://issues.apache.org/jira/browse/CLOUDSTACK-5902
Regards,
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
