Re: Upgrade from 4.1.1 to 4.2 failed. Could not restart system VMs. Roll back to 4.1.1 backup initially failed: could not start management service. Finally got it to work. I hope this helps someone el

On Oct 16, 2013, at 10:48 AM, Milamber milam...@apache.org wrote: Hello, curl: (7) couldn't connect to host Your integration.api.port isn't define in your global settings. See below. Current instructions to upgrade from 4.1.1 to 4.2 are not complete on official docs (missing 2

Re: Upgrade from 4.1.1 to 4.2 failed. Could not restart system VMs. Roll back to 4.1.1 backup initially failed: could not start management service. Finally got it to work. I hope this helps someone el

Hi, This post might help you out. http://cloud.kelceydamage.com/cloudfire/blog/2013/10/08/conquering-the-cloudstack-4-2-dragon-kvm/ If you need further help, please let me know. -Kelcey Sent from my HTC - Reply message - From: sebgoa run...@gmail.com To: users@cloudstack.apache.org,

Re: Upgrade from 4.1.1 to 4.2 failed. Could not restart system VMs. Roll back to 4.1.1 backup initially failed: could not start management service. Finally got it to work. I hope this helps someone el

Hi Adam, I also run into the same issues with upgrade from 4.0.0 to 4.2, on test CS installation, and was really pissed off, because of documentation is kind of incomplete on the upgrade process, or at least really buggy.. but I managed to resolve it for now ! 1. So if you want to try upgrade

Re: Upgrade from 4.1.1 to 4.2 failed. Could not restart system VMs. Roll back to 4.1.1 backup initially failed: could not start management service. Finally got it to work. I hope this helps someone el

Hi Guys ! Do you mean that Cloudstack 4.2 is not production ready ? Or is it the upgrade procedure towards a cs 4.2 that is not production ready ? Thanks for your responses. Regards, Benoit. 2013/10/16 Andrija Panic andrija.pa...@gmail.com Hi Adam, I also run into the same issues with

Re: Upgrade from 4.1.1 to 4.2 failed. Could not restart system VMs. Roll back to 4.1.1 backup initially failed: could not start management service. Finally got it to work. I hope this helps someone el

Correct On Oct 16, 2013 1:54 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: H Adam, forgive me if I missed some important clue in your report. It seems to me that it is the upgrade procedure that is not production ready, not version 4.2. Am I right? regards, Daan On Tue, Oct 15, 2013

Re: Upgrade from 4.1.1 to 4.2 failed. Could not restart system VMs. Roll back to 4.1.1 backup initially failed: could not start management service. Finally got it to work. I hope this helps someone el

H Adam, forgive me if I missed some important clue in your report. It seems to me that it is the upgrade procedure that is not production ready, not version 4.2. Am I right? regards, Daan On Tue, Oct 15, 2013 at 11:10 PM, Adam adam.scarce...@gmail.com wrote: I upgraded my 4 host private dev