vladimirpetrov opened a new issue #4502:
URL: https://github.com/apache/cloudstack/issues/4502
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
~~~
Upgrade
~~~
##### CLOUDSTACK VERSION
~~~
Upgrade from 4.14 to 4.15
~~~
##### CONFIGURATION
2 hosts using XenServer 7.0/7.1
##### OS / ENVIRONMENT
XenServer 7.0(7.1), two hypervisor hosts, CentOS 7.6 as management server
OS, CentOS 7.0 on the hosts.
##### SUMMARY
After upgrading from 4.14 to 4.15 and destroying the system VMs, they are
not able to start again.
##### STEPS TO REPRODUCE
~~~
1. Install CloudStack 4.14 with XenServer 7.0 (7.1), create some test
objects - VMs, snapshots, networks, etc.
2. Follow the standard upgrade procedure
3. After the upgrade, destroy the system VMs (as described in the
documentation)
~~~
##### EXPECTED RESULTS
~~~
Successful upgrade.
~~~
##### ACTUAL RESULTS
~~~
The new system VMs are not able to start, here is what is shown in the log:
2020-11-18 21:48:00,312 ERROR [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-8:ctx-5c32b189 job-71/job-72 ctx-c90dd860) (logid:84ab8c0f)
Failed to start instance VM[DomainRouter|r-14-VM]
com.cloud.utils.exception.ExecutionException: Unable to start
VM:4acfa807-b78e-48f0-b615-177c9a9c954d due to error in finalizeStart, not
retrying
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1266)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5461)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5628)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
After some investigations with @rhtyd, it turned out the reason is that the
systemvm.iso file is not detected by the host VM:
~~~
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
