Thanks Harikrishna,
it worked just fine
On Thu, Aug 1, 2013 at 11:12 PM, Daan Hoogland wrote:
> I did a 4.0 -> 4.1.1 -> master
> I can/will go back to 4.0 and report my findings tomorrow
>
> On Thu, Aug 1, 2013 at 8:02 PM, Harikrishna Patnala
> wrote:
>> Have you taken the DB dump before trying
I did a 4.0 -> 4.1.1 -> master
I can/will go back to 4.0 and report my findings tomorrow
On Thu, Aug 1, 2013 at 8:02 PM, Harikrishna Patnala
wrote:
> Have you taken the DB dump before trying to upgrade.
> Then you can build CS in 4.1.1 and apply the dump.
>
> -Harikrishna
>
> On 01-Aug-2013, at 8
Have you taken the DB dump before trying to upgrade.
Then you can build CS in 4.1.1 and apply the dump.
-Harikrishna
On 01-Aug-2013, at 8:42 PM, Daan Hoogland wrote:
> I have allready run master against this dev env, and added the
> mentioned entry in the upgrade map. Now I cannot access the da
I have allready run master against this dev env, and added the
mentioned entry in the upgrade map. Now I cannot access the database
using 4.1.1 anymore because of
ERROR [agent.manager.AgentManagerImpl] (AgentTaskPool-1:) Monitor
StoragePoolMonitor says there is an error in the connect process for 3
My comments inline.
Thanks
Harikrishna
On 01-Aug-2013, at 7:05 PM, Daan Hoogland
wrote:
> Harikrishna,
>
> I suppose I have to register those templates before upgrading; i.e. in
> the 4.1.1 version management server.
Yes. in 4.1.1 these templates are registered as USER templates. During upgrad
Harikrishna,
I suppose I have to register those templates before upgrading; i.e. in
the 4.1.1 version management server.
Is this procedure described somewhere?
Do I bake the templates myself first or should I use publicly offered templates?
thanks,
Daan
On Thu, Aug 1, 2013 at 3:16 PM, Harikrishn
Hi Daan,
Before upgrading to 4.2 we need to register the new system templates for each
hypervisor with specific names so that during upgrade these new templates are
set to the system vms.
It is mandatory to upgrade the system vm template if we want upgrade to 4.2.
Here seems like you have a Xen
H,
I am testing an upgrade of my code for sdn based vpc private gateways
(not in the mainstream code). It runs on a custom 4.1.1 based on the
4.1 branch. I have tested it against a 4.0 database and it upgrades
fine.
Now I try to have a master version to which I applied my code to run
against the
