Re: Systems VM Agent status-disconnect after upgrading from Cloudstack 4.1 to 4.2

2014-04-07 Thread Rafael Weingartner
Have you added the new system VM template into the CS before you start the upgrade process? On Fri, Apr 4, 2014 at 1:00 PM, Xerex Bueno wrote: > Yes, also if I remember correctly it actually tells you to do that in the > upgrade documentation. In the event it doesn't automatically recreate it, >

Re: Systems VM Agent status-disconnect after upgrading from Cloudstack 4.1 to 4.2

2014-04-04 Thread Xerex Bueno
Yes, also if I remember correctly it actually tells you to do that in the upgrade documentation. In the event it doesn't automatically recreate it, restart the CA management service. Sent from my iPhone > On Apr 4, 2014, at 10:57 AM, "motty cruz" wrote: > > hello Xerex, do you mean destroying

Re: Systems VM Agent status-disconnect after upgrading from Cloudstack 4.1 to 4.2

2014-04-04 Thread motty cruz
hello Xerex, do you mean destroying the Systems VMs? I did that once testing environment and CS never recreated, so i'm afraid to do so now in production environment. On Fri, Apr 4, 2014 at 8:53 AM, Xerex Bueno wrote: > Have you tried destroying the instance and allowing CS to create another > o

Re: Systems VM Agent status-disconnect after upgrading from Cloudstack 4.1 to 4.2

2014-04-04 Thread Xerex Bueno
Have you tried destroying the instance and allowing CS to create another one for you? > On Apr 4, 2014, at 10:45 AM, "motty cruz" wrote: > > Hello all, I upgrade Cloudstack 4.1 to Cloudstack 4.2, after upgrading > Systems VMs status show as Agent disconnect. > > for that reason I can't access