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

2013-10-18 Thread sebgoa
On Oct 18, 2013, at 3:47 PM, "kel...@backbonetechnology.com" wrote: > 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, did you read Milambe

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

2013-10-18 Thread kel...@backbonetechnology.com
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" To: , "Kelcey Jamison Damage" , "Travis Graham"

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

2013-10-18 Thread sebgoa
On Oct 16, 2013, at 10:48 AM, Milamber 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 important step

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

2013-10-16 Thread Adam
Correct On Oct 16, 2013 1:54 AM, "Daan Hoogland" 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 at 11:10 PM,

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

2013-10-16 Thread Milamber
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 important steps before upgrade). https://cloudstack.apache.org/docs/en-US/Apac

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

2013-10-16 Thread Nux!
On 16.10.2013 09:06, benoit lair wrote: 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 ? It depends how you look at it and how much "product upgradability" counts towards its "production readines

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

2013-10-16 Thread benoit lair
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 > Hi Adam, > > I also run into the same issues with upgrade from 4.0.0 to 4.

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

2013-10-16 Thread Andrija Panic
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 aga

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

2013-10-15 Thread Daan Hoogland
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 wrote: > I upgraded my 4 host private dev cloud running on CentOS 6.