Ian, I've successfully upgraded and downgraded acs on many occasions and it works like a charm as long as you perform the dump of cloud and cloud_usage databases and make sure you are using systemvm for the correct release. There is no need to wipe and reinstall unless you are testing acs and it is just quicker that way. If you are just testing, i suggest creating a base install with your initial configuration and snapshotting the acs server, so that you can easily return back the snapshot with a single command.
In order to login to the system vms you need to make sure you are using the Link Local IP address. Get the information on the ssvm and retrieve the name of the host where it runs and the Link Local IP address of the ssvm. Login to the host and run: ssh root@<Link local ip of ssvm> -i /root/.ssh/id_rsa.cloud -p 3922 The ssh service is running on port 3922 I believe. Once logged in, find the script called ssvm-check.sh or something like that and run it. Look for any errors, etc. If everything is working okay, most likely you have an issue with your systemvm templates. perhaps it is still using the template from the other release. Make sure your templates have been downloaded and also check out the Global Settings variable router.template.<hypervisor type> , to make sure it points to the right template. If not, change the above variable values and restart the management server. This should help Andrei ----- Original Message ----- > From: "Ian Young" <iyo...@ratespecial.com> > To: users@cloudstack.apache.org > Sent: Saturday, 4 October, 2014 12:14:13 AM > Subject: Re: upgraded to 4.4.1, management console is broken > Since the database had allegedly not been upgraded, I downgraded to > 4.4.0. > The management console was now available but I can't start instances. > Thinking I would have to back up all the instances and reinstall > CloudStack > from scratch again, I converted one of the instances to a template > but was > unable to download it. The browser times out while trying to connect > to > the SSVM. I can't connect to the SSVM using the RSA key either, > although > the console proxy shows it up and running, with the login prompt. I > port > scanned the SSVM and the only ports open were 80 and 443, not 22. > On Fri, Oct 3, 2014 at 1:51 PM, Ian Young <iyo...@ratespecial.com> > wrote: > > It looks like this is the root of the problem: > > > > 2014-10-03 13:44:47,131 DEBUG [c.c.u.d.Upgrade440to441] (main:null) > > Updating System Vm template IDs > > 2014-10-03 13:44:47,136 DEBUG [c.c.u.d.Upgrade440to441] (main:null) > > Updating LXC System Vms > > 2014-10-03 13:44:47,137 WARN [c.c.u.d.Upgrade440to441] (main:null) > > 4.4.0 > > LXC SystemVm template not found. LXC hypervisor is not used, so not > > failing > > upgrade > > 2014-10-03 13:44:47,138 DEBUG [c.c.u.d.Upgrade440to441] (main:null) > > Updating KVM System Vms > > 2014-10-03 13:44:47,141 ERROR [c.c.u.DatabaseUpgradeChecker] > > (main:null) > > Unable to upgrade the database > > com.cloud.utils.exception.CloudRuntimeException: 4.4.0 KVM SystemVm > > template not found. Cannot upgrade system Vms > > > > Any ideas about how I can fix this? I had a 4.4.0 KVM SystemVm > > template > > prior to the upgrade. > > > > On Fri, Oct 3, 2014 at 1:39 PM, Ian Young <iyo...@ratespecial.com> > > wrote: > > > >> I tried upgrading from 4.4.0 to 4.4.1 but now I get a 404 error > >> when I > >> try to access the management console. The localhost.2014-10-03.log > >> shows > >> this error: > >> > >> Caused by: java.io.IOException: Resource > >> [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-api-4.4.1.jar!/META-INF/cloudstack/api-config/module.properties] > >> and > >> [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-api-4.4.0.jar!/META-INF/cloudstack/api-config/module.properties] > >> do not appear to be the same resource, please ensure the name > >> property is > >> correct or that the module is not defined twice > >> > >> Where is this value defined? The full log can be viewed here: > >> > >> pastebin.com/nrdEsxZK > >> > >> I also noticed the error "4.4.0 KVM SystemVm template not found. > >> Cannot > >> upgrade system Vms." The URL for the system VM template in the > >> 4.4.1 > >> upgrade instructions is the same as the one I used when I > >> installed 4.4.0 > >> initially. Is there really a need to install the same template > >> again? > >> > > > >
