Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Rohit Yadav
Architect, ShapeBlue https://www.shapeblue.com From: Jevgeni Zolotarjov Sent: Thursday, July 4, 2019 2:28:37 PM To: users@cloudstack.apache.org Subject: Re: failure after update 4.11.2 -> 4.11.3 I downgraded cloudstack to 4.11.2 But apparently as the result

Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Jevgeni Zolotarjov
s://www.shapeblue.com > > > From: Jevgeni Zolotarjov > Sent: Thursday, July 4, 2019 11:40:16 AM > To: users@cloudstack.apache.org > Subject: failure after update 4.11.2 -> 4.11.3 > > Hello > > I followed installation steps as des

Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Rohit Yadav
From: Jevgeni Zolotarjov Sent: Thursday, July 4, 2019 11:40:16 AM To: users@cloudstack.apache.org Subject: failure after update 4.11.2 -> 4.11.3 Hello I followed installation steps as described here http://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.11.htm

Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Andrija Panic
That is an "old" bug with original RC1 4.11.3 release, please check the newest packaging, there might be already built - check the "[VOTE][RESULT] Apache CloudStack 4.11.3.0" thread and latest reply from Rohit on packages built. On Thu, 4 Jul 2019 at 12:27, Boris Stoyanov wrote: > If you have a

Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Boris Stoyanov
If you have a backup I suggest you downgrade and do it from scratch, if not you can do some DB hacking to fake it that the template is good to go, so it can carry on with the upgrade. If I were you, I would choose to roll-back the db and packages to 4.11.2 and do the upgrade again. Thanks,

Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Jevgeni Zolotarjov
I checked that it is in READY state Anyway. What to do now? On Thu, Jul 4, 2019 at 10:03 AM Boris Stoyanov wrote: > Hi Jevgeni, > > Did you made sure your 4.11.3 systemvm template is installed and usable > before diving into upgrade? > > Looks like cloudstack cannot find a 4.11.3 template to

Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Boris Stoyanov
Hi Jevgeni, Did you made sure your 4.11.3 systemvm template is installed and usable before diving into upgrade? Looks like cloudstack cannot find a 4.11.3 template to carry on the template. Thanks, Bobby. On 4.07.19, 9:10, "Jevgeni Zolotarjov" wrote: Hello I followed

failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Jevgeni Zolotarjov
Hello I followed installation steps as described here http://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.11.htm I made sure, that system VM templates were in READY state. But after update management server does not start ● cloudstack-management.service - CloudStack