Thanks Zack, But as I mentioned this was not an upgrade this was a fresh install of 4.3. Which according to the latest "Quick Installation for CentOS" documentation it says to install the systemvms using cloud-install-sys-tmplt command.
Anyways I went through some one the steps in the 4.2.x to 4.3 section to see if it would help get me to 4.3 systemvms. Here is what I did. Followed step 1 to register the new system template for xenserver I stopped the cloudstack-managment service I do no use the cloudstack-usage service yet Since I am already running cloudstack 4.3 from a fresh yum install I skipped the yum steps. But here is proof. [root@stacktest1 management]# rpm -qa |grep cloud cloudstack-awsapi-4.3.0-1.el6.x86_64 cloudstack-common-4.3.0-1.el6.x86_64 cloudstack-management-4.3.0-1.el6.x86_64 [root@stacktest1 management]# cat /etc/yum.repos.d/cloudstack.repo [cloudstack] name=cloudstack baseurl=http://cloudstack.apt-get.eu/rhel/4.3/ enabled=1 gpgcheck=0 Started cloudstack-managment service Last ran the sysvmadm script. nohup cloudstack-sysvmadm -d IP address -u cloud -p -a > sysvm.log 2>&1 & [root@stacktest1 management]# tail -f sysvm.log nohup: ignoring input Stopping and starting 1 secondary storage vm(s)... Done stopping and starting secondary storage vm(s) Stopping and starting 1 console proxy vm(s)... Done stopping and starting console proxy vm(s) . Stopping and starting 1 running routing vm(s)... Done restarting router(s). Oh yeah also ls /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-util* /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-util /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-utils This is killing me... My system VM's are still at 4.2 On Wed, May 28, 2014 at 1:31 PM, Zack <[email protected]> wrote: > I think that rather than using the cloud-install-sys-tmplt command, it's > recommended to use the web UI as documented in the 4.3 release notes > upgrade from 4.2.x to 4.3 section. > > Z > > > On May 28, 2014, at 9:19 AM, Derek Page <[email protected]> wrote: > > > > From a fresh install of cloudstack 4.3 and installing the 4.3 system vms > > from download.cloud.com > > > http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2 > > > > If you look at the system vms their /etc/cloudstack-version is still 4.2 > > root@r-21-VM:~# cat /etc/cloudstack-release > > Cloudstack Release 4.2.0 Tue Jul 16 04:16:55 UTC 2013 > > > > > > This was causing a failure to deploy instances with the following stack > > trace. > > > > Caused by: com.cloud.exception.AgentUnavailableException: Resource > [Host:5] > > is unreachable: Host 5: Unable to start instance due to Unable to send > > command. Upgrade in progress. Please contact administrator. > > at > > > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1072) > > at > > > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) > > at > > > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:601) > > ... 37 more > > Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to > send > > command. Upgrade in progress. Please contact administrator. > > at > > > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.sendCommandsToRouter(VirtualNetworkApplianceManagerImpl.java:3616) > > at > > > com.cloud.network.router.VirtualNetworkApplianceManagerImpl$7.execute(VirtualNetworkApplianceManagerImpl.java:3051) > > at > > > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3903) > > at > > > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:3043) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:606) > > at > > > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > > at > > > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > > at > > > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > > at > > > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > > at > > > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > > at > > > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > > at com.sun.proxy.$Proxy240.applyDhcpEntry(Unknown Source) > > at > > > com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:921) > > at > > > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareElement(NetworkOrchestrator.java:1187) > > at > > > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1309) > > at > > > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1245) > > at > > > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:960) > > ... 39 more > > > > > > So from here I. > > Destroyed/Expunged all systemvm's > > Removed the secondary storage in cloudstack > > rm -fr /mnt/secondary/* > > recreated the secondary storage in cloudstack > > Pulled the systemvms back down using this command: > > $ sudo > > > /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt > > -m /secondary -u > > > http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2-h > > xenserver -F > > > > But still the systemvm's are at version 4.2 > > > > Next I manually hacked /etc/cloudstack-version to be 4.3 instead of 4.2 > on > > the router and I was able to deploy instances. > > This is my only work around at the moment. > > > > Is there a later version of the system VM's? > > Or did someone forget to bump versions in /etc/cloudstack-version? > > Or am I completely doing something wrong? > > > > -- > > Derek Page > > Operations Engineer > > KAYAK > -- Derek Page Operations Engineer KAYAK
