RE: Upgrade 3.0.2->4.0.0

2012-11-12 Thread Tamas Monos
[mailto:kishan.kav...@citrix.com] Sent: 09 November 2012 18:16 To: cloudstack-dev@incubator.apache.org Cc: cloudstack-dev@incubator.apache.org Subject: Re: Upgrade 3.0.2->4.0.0 Tamas, Below column has to be added in cloud_usage db for usage server to work. mysql> ALTER TABLE `cloud_usage`.`account` ADD

Re: Upgrade 3.0.2->4.0.0

2012-11-09 Thread Kishan Kavala
age- From: Kishan Kavala [mailto:kishan.kav...@citrix.com] Sent: 08 November 2012 18:24 To: cloudstack-dev@incubator.apache.org<mailto:cloudstack-dev@incubator.apache.org> Subject: RE: Upgrade 3.0.2->4.0.0 Tamas, Looks like vmware systemVm template upgrade is missing in 4.0 upgrade.

RE: Upgrade 3.0.2->4.0.0

2012-11-09 Thread Tamas Monos
08 November 2012 18:24 To: cloudstack-dev@incubator.apache.org Subject: RE: Upgrade 3.0.2->4.0.0 Tamas, Looks like vmware systemVm template upgrade is missing in 4.0 upgrade. You can try the below work around: 1. Add new vmware template to CS with name systemvm-vmware-4.0 2. Wait till th

RE: Upgrade 3.0.2->4.0.0

2012-11-08 Thread Kishan Kavala
Thursday, November 08, 2012 7:39 PM To: cloudstack-dev@incubator.apache.org Subject: Upgrade 3.0.2->4.0.0 Hi, Sorry putting this on dev-list but got no luck on the user one. I have upgraded from 3.0.2 to 4.0.0 and the management server started and updated the database just fine, however the rest of the upg

Re: Upgrade 3.0.2->4.0.0

2012-11-08 Thread Caleb Call
This is the exact same case for my upgrade as well. One thing I noticed in the log file is it claims the -c option is not a valid option. # cat sysvm.log nohup: ignoring input /usr/bin/cloud-sysvmadm: illegal option -- c Stopping and starting 1 running routing vm(s)... Done restarting router(

Upgrade 3.0.2->4.0.0

2012-11-08 Thread Tamas Monos
Hi, Sorry putting this on dev-list but got no luck on the user one. I have upgraded from 3.0.2 to 4.0.0 and the management server started and updated the database just fine, however the rest of the upgrade procedure just does not work. I'm running the script: "nohup cloud-sysvmadm -d 192.168.1.