Alena Prokharchyk wrote:
> Just one thing was missing - upgrade path from 4.4.1->4.5, I’ve added it
> to DataBaseUpgradeChecker:
>
> _upgradeMap.put("4.4.1", new DbUpgrade[] { new Upgrade441to450() });
Thanks for catching that and fixing it.
Regards.
>
>
> -Alena.
>
> On 7/28/14, 3:26 PM, "Alen
Just one thing was missing - upgrade path from 4.4.1->4.5, I’ve added it
to DataBaseUpgradeChecker:
_upgradeMap.put("4.4.1", new DbUpgrade[] { new Upgrade441to450() });
-Alena.
On 7/28/14, 3:26 PM, "Alena Prokharchyk"
wrote:
>Will do, thank you, Rohit.
>
>-Alena.
>
>On 7/28/14, 3:23 PM, "Rohi
Will do, thank you, Rohit.
-Alena.
On 7/28/14, 3:23 PM, "Rohit Yadav" wrote:
>Hi Alena,
>
>I've changed the upgrade path from 4.4.1 to 4.5.0, please verify at your
>end especially the DatabaseUpgradeChecker since there are too many list
>of upgrade path class changes.
>
>On master: d42e20429d1e
Hi Alena,
I've changed the upgrade path from 4.4.1 to 4.5.0, please verify at your
end especially the DatabaseUpgradeChecker since there are too many list
of upgrade path class changes.
On master: d42e20429d1e238816a07edd865567c06a4914d3
Regards.
Alena Prokharchyk wrote:
The upgrade path shou
The upgrade path should also be merged to master branch. Where btw I
already see an upgrade path from 4.4 to 4.5 implemented. Should we change
it to 4.4.1->4.5?
-Alena.
On 7/28/14, 2:54 PM, "Rohit Yadav" wrote:
>Hi,
>
>Adding upgrade paths is simple (you may add/update a wiki page on it):
>
>-
Hi,
Adding upgrade paths is simple (you may add/update a wiki page on it):
- You add a upgrade path class under com.cloud.upgrade.dao, something
like UpgradeVERAtoVERb, in our case Upgrade440to441 which should
implement the interface DbUpgrade. If there is some complex migration
you need to do i
If there is documentation for how to do this somewhere, I could implement
an empty upgrade path. Do we know if there are database changes needed for
the 4.4.1 upgrade from 4.4.0? How would that requirement be captured?
Cheers,
Will
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions
Will,
this is a bug due to our upgrade scheme: we have not yet implemented
it so it is missing. We need to implement some (possibly empty)
upgrade path to make sure this will still work for 4.4.1.
On Mon, Jul 28, 2014 at 9:46 PM, Will Stevens wrote:
> I am guessing this is a bug, but I want to p
I am guessing this is a bug, but I want to post it here before I create a
ticket. I have pulled down the latest code from the 4.4 branch (which
results in the 4.4.1 release).
I am able to compile the code without any issues, but when I run the
following command to deploy my DB it fails.
$ mvn -P
