[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413187#comment-16413187 ] Mohit Sharma commented on CLOUDSTACK-9144: -- Just an update — This bug still persists in Cloudstack 4.11 (LTS). > VMware in Basic Zone: VR never leaves the "Starting" state > -- > > Key: CLOUDSTACK-9144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router, VMware >Affects Versions: 4.6.0, 4.7.0 > Environment: Management server running on Ubuntu 12.04 > Secondary storage being served off of the same computer as that which was > running the management server >Reporter: Mike Tutkowski >Priority: Major > Fix For: Future > > Attachments: cloud.log, syslog, vmops.log > > > I fetched the latest code and checked out the 4.6 branch. > The code was compiled as such: > mvn -P developer,systemvm clean install -D noredist > I grabbed the latest system VM template from http://jenkins.buildacloud.org/. > I walked through the new-zone wizard (creating a basic zone) and tried to > make use of it with two ESXi 5.5 hosts (under the control of vCenter Server). > The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off > my first user VM) never exited the "Starting" state. > I repeated this same process for 4.7 and arrived at the same results. > I then fell back to 4.5, repeated the process, and was successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112002#comment-16112002 ] Mike Tutkowski commented on CLOUDSTACK-9144: I was able to get the VR into the Started state using Paul's method; however, I was not able to get a user VM running: com.cloud.exception.ResourceUnavailableException: Resource [VirtualRouter:42] is unreachable: Unable to send command. Router requires upgrade at com.cloud.network.router.NetworkHelperImpl.sendCommandsToRouter(NetworkHelperImpl.java:168) at org.apache.cloudstack.network.topology.BasicNetworkVisitor.visit(BasicNetworkVisitor.java:203) at com.cloud.network.rules.DhcpEntryRules.accept(DhcpEntryRules.java:62) at org.apache.cloudstack.network.topology.BasicNetworkTopology.applyRules(BasicNetworkTopology.java:390) at org.apache.cloudstack.network.topology.BasicNetworkTopology.applyDhcpEntry(BasicNetworkTopology.java:163) at com.cloud.network.element.VirtualRouterElement.applyDhcpEntries(VirtualRouterElement.java:1084) at com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:1052) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareElement(NetworkOrchestrator.java:1275) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1584) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1518) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1005) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4742) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4903) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:558) 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 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:506) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-12:ctx-6341a43d job-501/job-503) (logid:bb593183) Remove job-503 from job monitoring WARN [o.a.c.alerts] (API-Job-Executor-6:ctx-c53b769f job-501 ctx-40f4551d) (logid:bb593183) AlertType:: 8 | dataCenterId:: 1 | podId:: 1 | clusterId:: null | message:: Failed to deploy Vm with Id: 44, on Host with Id: null ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-6:ctx-c53b769f job-501) (logid:bb593183) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin com.cloud.utils.exception.CloudRuntimeException: Network is unavailable. Please contact administrator at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:628) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:245) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:212) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4174) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3753) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3741) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833552#comment-15833552 ] haijiao commented on CLOUDSTACK-9144: - This is reported by many users, would appreciate if any dev. can take a look at this . > VMware in Basic Zone: VR never leaves the "Starting" state > -- > > Key: CLOUDSTACK-9144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router, VMware >Affects Versions: 4.6.0, 4.7.0 > Environment: Management server running on Ubuntu 12.04 > Secondary storage being served off of the same computer as that which was > running the management server >Reporter: Mike Tutkowski > Fix For: Future > > Attachments: cloud.log, syslog, vmops.log > > > I fetched the latest code and checked out the 4.6 branch. > The code was compiled as such: > mvn -P developer,systemvm clean install -D noredist > I grabbed the latest system VM template from http://jenkins.buildacloud.org/. > I walked through the new-zone wizard (creating a basic zone) and tried to > make use of it with two ESXi 5.5 hosts (under the control of vCenter Server). > The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off > my first user VM) never exited the "Starting" state. > I repeated this same process for 4.7 and arrived at the same results. > I then fell back to 4.5, repeated the process, and was successful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832950#comment-15832950 ] Özhan Rüzgar Karaman commented on CLOUDSTACK-9144: -- 4.9.2 version also effects from this problem, vr never leaves on starting state. Do we have any workaround on this problem... > VMware in Basic Zone: VR never leaves the "Starting" state > -- > > Key: CLOUDSTACK-9144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router, VMware >Affects Versions: 4.6.0, 4.7.0 > Environment: Management server running on Ubuntu 12.04 > Secondary storage being served off of the same computer as that which was > running the management server >Reporter: Mike Tutkowski > Fix For: Future > > Attachments: cloud.log, syslog, vmops.log > > > I fetched the latest code and checked out the 4.6 branch. > The code was compiled as such: > mvn -P developer,systemvm clean install -D noredist > I grabbed the latest system VM template from http://jenkins.buildacloud.org/. > I walked through the new-zone wizard (creating a basic zone) and tried to > make use of it with two ESXi 5.5 hosts (under the control of vCenter Server). > The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off > my first user VM) never exited the "Starting" state. > I repeated this same process for 4.7 and arrived at the same results. > I then fell back to 4.5, repeated the process, and was successful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421797#comment-15421797 ] Mike Tutkowski commented on CLOUDSTACK-9144: Any other file you would like me to upload while I have this configured? > VMware in Basic Zone: VR never leaves the "Starting" state > -- > > Key: CLOUDSTACK-9144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router, VMware >Affects Versions: 4.6.0, 4.7.0 > Environment: Management server running on Ubuntu 12.04 > Secondary storage being served off of the same computer as that which was > running the management server >Reporter: Mike Tutkowski > Fix For: Future > > Attachments: vmops.log > > > I fetched the latest code and checked out the 4.6 branch. > The code was compiled as such: > mvn -P developer,systemvm clean install -D noredist > I grabbed the latest system VM template from http://jenkins.buildacloud.org/. > I walked through the new-zone wizard (creating a basic zone) and tried to > make use of it with two ESXi 5.5 hosts (under the control of vCenter Server). > The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off > my first user VM) never exited the "Starting" state. > I repeated this same process for 4.7 and arrived at the same results. > I then fell back to 4.5, repeated the process, and was successful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421790#comment-15421790 ] Mike Tutkowski commented on CLOUDSTACK-9144: Yes, there exist a sufficient number of IP addresses for system VMs. I can upload the vmops.log file. Thanks! > VMware in Basic Zone: VR never leaves the "Starting" state > -- > > Key: CLOUDSTACK-9144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router, VMware >Affects Versions: 4.6.0, 4.7.0 > Environment: Management server running on Ubuntu 12.04 > Secondary storage being served off of the same computer as that which was > running the management server >Reporter: Mike Tutkowski > Fix For: Future > > > I fetched the latest code and checked out the 4.6 branch. > The code was compiled as such: > mvn -P developer,systemvm clean install -D noredist > I grabbed the latest system VM template from http://jenkins.buildacloud.org/. > I walked through the new-zone wizard (creating a basic zone) and tried to > make use of it with two ESXi 5.5 hosts (under the control of vCenter Server). > The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off > my first user VM) never exited the "Starting" state. > I repeated this same process for 4.7 and arrived at the same results. > I then fell back to 4.5, repeated the process, and was successful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391372#comment-15391372 ] sadhu suresh commented on CLOUDSTACK-9144: -- do you have enough public and private IPs . also please upload the logs. regards sadhu > VMware in Basic Zone: VR never leaves the "Starting" state > -- > > Key: CLOUDSTACK-9144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router, VMware >Affects Versions: 4.6.0, 4.7.0 > Environment: Management server running on Ubuntu 12.04 > Secondary storage being served off of the same computer as that which was > running the management server >Reporter: Mike Tutkowski > Fix For: Future > > > I fetched the latest code and checked out the 4.6 branch. > The code was compiled as such: > mvn -P developer,systemvm clean install -D noredist > I grabbed the latest system VM template from http://jenkins.buildacloud.org/. > I walked through the new-zone wizard (creating a basic zone) and tried to > make use of it with two ESXi 5.5 hosts (under the control of vCenter Server). > The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off > my first user VM) never exited the "Starting" state. > I repeated this same process for 4.7 and arrived at the same results. > I then fell back to 4.5, repeated the process, and was successful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316826#comment-15316826 ] Mike Tutkowski commented on CLOUDSTACK-9144: Unfortunately, no update as of yet. It looks like the ticket is still in the Unassigned state, as well. > VMware in Basic Zone: VR never leaves the "Starting" state > -- > > Key: CLOUDSTACK-9144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router, VMware >Affects Versions: 4.6.0, 4.7.0 > Environment: Management server running on Ubuntu 12.04 > Secondary storage being served off of the same computer as that which was > running the management server >Reporter: Mike Tutkowski > Fix For: Future > > > I fetched the latest code and checked out the 4.6 branch. > The code was compiled as such: > mvn -P developer,systemvm clean install -D noredist > I grabbed the latest system VM template from http://jenkins.buildacloud.org/. > I walked through the new-zone wizard (creating a basic zone) and tried to > make use of it with two ESXi 5.5 hosts (under the control of vCenter Server). > The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off > my first user VM) never exited the "Starting" state. > I repeated this same process for 4.7 and arrived at the same results. > I then fell back to 4.5, repeated the process, and was successful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299760#comment-15299760 ] darrentang commented on CLOUDSTACK-9144: any update? > VMware in Basic Zone: VR never leaves the "Starting" state > -- > > Key: CLOUDSTACK-9144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router, VMware >Affects Versions: 4.6.0, 4.7.0 > Environment: Management server running on Ubuntu 12.04 > Secondary storage being served off of the same computer as that which was > running the management server >Reporter: Mike Tutkowski > Fix For: Future > > > I fetched the latest code and checked out the 4.6 branch. > The code was compiled as such: > mvn -P developer,systemvm clean install -D noredist > I grabbed the latest system VM template from http://jenkins.buildacloud.org/. > I walked through the new-zone wizard (creating a basic zone) and tried to > make use of it with two ESXi 5.5 hosts (under the control of vCenter Server). > The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off > my first user VM) never exited the "Starting" state. > I repeated this same process for 4.7 and arrived at the same results. > I then fell back to 4.5, repeated the process, and was successful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
