cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Gowar <...@whiteheat.org.uk>
Subject System / Virtual router VM state after 4.2 to 4.3 upgrade
Date Tue, 08 Apr 2014 10:31:30 GMT
Hi,

  I had an issue with the router VM on 4.2 and thought upgrading to 4.3
might resolve that.  So, I deleted the router VM and upgraded.

Now booting on 4.3, it appears the UI has upgraded, but I have no router
VM, 2x secondary storage VMs (1 UP and the other Disconnected and
Expunging), and 1x Console Proxy VM that won't start:-

2014-04-08 11:29:48,065 DEBUG [c.c.c.CapacityManagerImpl]
(consoleproxy-1:ctx-a09815ec) release mem from host: 4, old used:
1073741824,reserved: 0, total: 16825044992; new used: 0,reserved:0;
movedfromreserved: false,moveToReserveredfalse
2014-04-08 11:29:48,149 WARN  [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-a09815ec) Exception while trying to start console
proxy
com.cloud.exception.AgentUnavailableException: Resource [Host:4] is
unreachable: Host 4: Unable to start instance due to can't find ready
template: 204 for data center 1
        at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1072)
        at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
        at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745)
        at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:555)
        at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:941)
        at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1666)
        at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157)
        at
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:118)
        at com.cloud.vm.SystemVmLoadScanner.access
$100(SystemVmLoadScanner.java:35)
        at com.cloud.vm.SystemVmLoadScanner
$1.reallyRun(SystemVmLoadScanner.java:88)
        at com.cloud.vm.SystemVmLoadScanner
$1.runInContext(SystemVmLoadScanner.java:79)
        at org.apache.cloudstack.managed.context.ManagedContextRunnable
$1.run(ManagedContextRunnable.java:49)
        at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext
$1.call(DefaultManagedContext.java:56)
        at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
        at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
        at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
        at java.util.concurrent.Executors
$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask
$Sync.innerRunAndReset(FutureTask.java:351)
        at
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor
$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
        at java.util.concurrent.ScheduledThreadPoolExecutor
$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
        at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:701)
Caused by: com.cloud.utils.exception.CloudRuntimeException: can't find
ready template: 204 for data center 1
        at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1188)
        at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1254)
        at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:962)
        ... 23 more



Help with all these issues would be appreciated.

Kind regards,
Jon


Mime
View raw message