I picked an arbitrary vlan range of 10-20 and defined this in my physical
network setting in the zone. This allowed me to launch a vm guest, but I can’t
ping its public interface.
I would expect at this point I would be able to ping the public interface, ssh
in, etc.
Thanks
> On May 31, 2021, at 4:30 AM, Jeremy Hansen <jer...@skidrow.la> wrote:
>
> Thank you. This vlan range only applies to the network between the vm guest
> and the vm host? Does this vlan range need to exist on my public net? The
> vlan stuff did confuse me a bit and I believe on my latest try, I didn’t
> define one.
>
> -jeremy
>
>> On May 31, 2021, at 4:14 AM, Nicolas Vazquez <nicolas.vazq...@shapeblue.com>
>> wrote:
>> Hi Jeremy,
>> Can you please check if you have a Vlan range defined for your guest
>> physical network? You can check under Infrastructure -> Zone -> Physical
>> Network -> Guest. In case the Vlan range is not defined you can update the
>> guest physical network's VLAN/VNI to the format: VLAN_START-VLAN_END
>> Regards,
>> Nicolas Vazquez
>> ________________________________
>> From: Jeremy Hansen
>> Sent: Monday, May 31, 2021 3:11 AM
>> To: users@cloudstack.apache.org
>> Subject: Re: Quickstart question - Network issues
>> Thank you for the response. I got much further. All my issues seem
>> networking related. Everything is up right now and I see the template for
>> CentOS 5.5 as an offering.
>> My Cloudstack host is on 192.168.10.35. My System VMs is configured as such:
>> [cid:D47FD2E4-F159-4778-973E-F96505D3ADD6]
>> At this point, I’m trying to understand how to configured my Guest networks.
>> Ideally my guest vm’s would just use my external DHCP server to allocate an
>> IP address but I’m not having much luck finding documentation on how to
>> properly do that. I also see posts saying external DHCP servers aren’t
>> supported because Cloudstack needs to be aware of the guest’s IP for a
>> number of reasons.
>> So my question becomes, what type and how should I configure my guest
>> network. Can I use IPs on the same subnet that my Cloudstack host is
>> sitting on? If I can’t use DHCP directly, I can specify a range that is not
>> in use by my external DHCP server so IPs will still end up on the public
>> network and I can access the VMs on that IP directly.
>> Interfaces on my Cloudstack host:
>> cloud0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
>> inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20<link>
>> ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet)
>> RX packets 440 bytes 80558 (78.6 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 539 bytes 96150 (93.8 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> cloudbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.10.35 netmask 255.255.255.0 broadcast 192.168.10.255
>> inet6 fe80::4a2:a9ff:fecf:819 prefixlen 64 scopeid 0x20<link>
>> ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet)
>> RX packets 1203750 bytes 3227151094 (3.0 GiB)
>> RX errors 0 dropped 5 overruns 0 frame 0
>> TX packets 498851 bytes 2710603584 (2.5 GiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet)
>> RX packets 4650048 bytes 4876148565 (4.5 GiB)
>> RX errors 0 dropped 622 overruns 0 frame 0
>> TX packets 3955493 bytes 5163648882 (4.8 GiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> device interrupt 20 memory 0xf7c00000-f7c20000
>> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
>> inet 127.0.0.1 netmask 255.0.0.0
>> inet6 ::1 prefixlen 128 scopeid 0x10<host>
>> loop txqueuelen 1000 (Local Loopback)
>> RX packets 2322050 bytes 504114946 (480.7 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 2322050 bytes 504114946 (480.7 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet6 fe80::fc00:a9ff:fefe:91b4 prefixlen 64 scopeid 0x20<link>
>> ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet)
>> RX packets 50 bytes 9384 (9.1 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 98 bytes 15290 (14.9 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet6 fe80::fc00:7cff:fe00:5 prefixlen 64 scopeid 0x20<link>
>> ether fe:00:7c:00:00:05 txqueuelen 1000 (Ethernet)
>> RX packets 15707 bytes 2225323 (2.1 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 127124 bytes 19795223 (18.8 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> vnet2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet6 fe80::fc00:d8ff:fe00:7 prefixlen 64 scopeid 0x20<link>
>> ether fe:00:d8:00:00:07 txqueuelen 1000 (Ethernet)
>> RX packets 808 bytes 57456 (56.1 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 109119 bytes 17746092 (16.9 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> vnet3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet6 fe80::fc00:a9ff:fefe:b767 prefixlen 64 scopeid 0x20<link>
>> ether fe:00:a9:fe:b7:67 txqueuelen 1000 (Ethernet)
>> RX packets 46 bytes 9168 (8.9 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 95 bytes 15068 (14.7 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> vnet4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet6 fe80::fc00:c2ff:fe00:6 prefixlen 64 scopeid 0x20<link>
>> ether fe:00:c2:00:00:06 txqueuelen 1000 (Ethernet)
>> RX packets 144923 bytes 2256458775 (2.1 GiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 822253 bytes 1009838617 (963.0 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> vnet5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet6 fe80::fc00:3fff:fe00:8 prefixlen 64 scopeid 0x20<link>
>> ether fe:00:3f:00:00:08 txqueuelen 1000 (Ethernet)
>> RX packets 55945 bytes 3044600 (2.9 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 172076 bytes 493393439 (470.5 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> I see this error in the manager logs:
>> 2021-05-30 23:02:38,566 INFO [c.c.v.VirtualMachineManagerImpl]
>> (Work-Job-Executor-40:ctx-af5db647 job-75/job-76 ctx-ec204ee7)
>> (logid:8f07205c) Insufficient capacity
>> com.cloud.exception.InsufficientVirtualNetworkCapacityException: Unable to
>> allocate vnet as a part of network Ntwk[207|Guest|14] implement
>> Scope=interface com.cloud.dc.DataCenter; id=1
>> at
>> com.cloud.network.guru.GuestNetworkGuru.allocateVnet(GuestNetworkGuru.java:296)
>> at
>> com.cloud.network.guru.GuestNetworkGuru.implement(GuestNetworkGuru.java:325)
>> at
>> com.cloud.network.guru.ExternalGuestNetworkGuru.implement(ExternalGuestNetworkGuru.java:136)
>> at
>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:1237)
>> at
>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:1176)
>> at
>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1767)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1149)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5464)
>> 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:5631)
>> 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:829)
>> 2021-05-30 23:02:39,388 ERROR [c.c.v.VmWorkJobDispatcher]
>> (Work-Job-Executor-40:ctx-af5db647 job-75/job-76) (logid:8f07205c) Unable to
>> complete AsyncJobVO {id:76, userId: 2, accountId: 2, instanceType: null,
>> instanceId: null, cmd: com.cloud.vm.VmWorkStart, cmdInfo:
>> rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAAAAAAAAAACAAAAAAAAAAIAAAAAAAAAC3QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAAAAAAAAAXBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAAFxAH4ACnBwcHEAfgAKcHNyABFqYXZhLnV0aWwuSGFzaE1hcAUH2sHDFmDRAwACRgAKbG9hZEZhY3RvckkACXRocmVzaG9sZHhwP0AAAAAAAAx3CAAAABAAAAABdAAKVm1QYXNzd29yZHQAHHJPMEFCWFFBRG5OaGRtVmtYM0JoYzNOM2IzSmt4cA,
>> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
>> result: null, initMsid: 156338647199026, completeMsid: null, lastUpdated:
>> null, lastPolled: null, created: Sun May 30 23:02:36 PDT 2021, removed:
>> null}, job origin:75
>> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
>> deployment for VM[User|i-2-11-VM]Scope=interface com.cloud.dc.DataCenter;
>> id=1
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1110)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5464)
>> 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:5631)
>> 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:829)
>> [cid:60D93672-2419-42B5-86F5-1DDF5F92A325]
>> Also noticed this error a few times:
>> Can't design network Ntwk[-1|Guest|8]; guest CIDR is not configured per zone
>> com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$dcf5c4f2@1
>> Request Failed (530)
>> Can't design network Ntwk[-1|Guest|8]; guest CIDR is not configured per zone
>> com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$dcf5c4f2@1
>> 2021-05-30 23:10:04,712 INFO [c.c.v.VirtualMachineManagerImpl]
>> (Work-Job-Executor-45:ctx-a21b3c03 job-85/job-86 ctx-f264d341)
>> (logid:a1c18342) Insufficient capacity
>> com.cloud.exception.InsufficientVirtualNetworkCapacityException: Unable to
>> allocate vnet as a part of network Ntwk[210|Guest|8] implement
>> Scope=interface com.cloud.dc.DataCenter; id=1
>> at
>> com.cloud.network.guru.GuestNetworkGuru.allocateVnet(GuestNetworkGuru.java:296)
>> at
>> com.cloud.network.guru.GuestNetworkGuru.implement(GuestNetworkGuru.java:325)
>> at
>> com.cloud.network.guru.ExternalGuestNetworkGuru.implement(ExternalGuestNetworkGuru.java:136)
>> at
>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:1237)
>> at
>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:1176)
>> at
>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1767)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1149)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5464)
>> 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:5631)
>> 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:829)
>> 2021-05-30 23:10:05,597 ERROR [c.c.v.VmWorkJobDispatcher]
>> (Work-Job-Executor-45:ctx-a21b3c03 job-85/job-86) (logid:a1c18342) Unable to
>> complete AsyncJobVO {id:86, userId: 2, accountId: 2, instanceType: null,
>> instanceId: null, cmd: com.cloud.vm.VmWorkStart, cmdInfo:
>> rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAAAAAAAAAACAAAAAAAAAAIAAAAAAAAADHQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAAAAAAAAAXBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAAFxAH4ACnBwcHEAfgAKcHNyABFqYXZhLnV0aWwuSGFzaE1hcAUH2sHDFmDRAwACRgAKbG9hZEZhY3RvckkACXRocmVzaG9sZHhwP0AAAAAAAAx3CAAAABAAAAABdAAKVm1QYXNzd29yZHQAHHJPMEFCWFFBRG5OaGRtVmtYM0JoYzNOM2IzSmt4cA,
>> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
>> result: null, initMsid: 156338647199026, completeMsid: null, lastUpdated:
>> null, lastPolled: null, created: Sun May 30 23:10:01 PDT 2021, removed:
>> null}, job origin:85
>> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
>> deployment for VM[User|i-2-12-VM]Scope=interface com.cloud.dc.DataCenter;
>> id=1
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1110)
>> at
>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5464)
>> 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:5631)
>> 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:829)
>> I think once I have an end to end working VM, things will make a lot more
>> sense to me.
>> Thank you
>> -jeremy
>> On May 30, 2021, at 7:01 PM, Harikrishna Patnala
>> <harikrishna.patn...@shapeblue.com<mailto:harikrishna.patn...@shapeblue.com>>
>> wrote:
>> Hi Jeremy,
>> May I know the NFS version number that you are using in your environment?
>> Also, check the status of the default template by clicking on the template
>> and then into the zones tab, to check if it is downloaded properly or not.
>> Regards,
>> Harikrishna
>> ________________________________
>> From: Jeremy Hansen
>> Sent: Sunday, May 30, 2021 4:51 PM
>> To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
>> Subject: Re: Quickstart question
>> Went over the process about 20 times and made progress. I’m able to launch
>> a VM as long as the template is a direct download bypassing secondary
>> storage. I see this in the logs:
>> 2021-05-30 04:01:57,148 DEBUG [c.c.a.t.Request]
>> (AgentManager-Handler-12:null) (logid:) Seq 2-4381439487478071309:
>> Processing: { Ans: , MgmtId: 198690285003419, via: 2, Ver: v1, Flags: 10,
>> [{"com.cloud.agent.api.Answer":{"result":"false","details":"com.cloud.utils.exception.CloudRuntimeException:
>> GetRootDir for nfs://192.168.10.60/volume1/cloudstack-dev/secondary failed
>> due to com.cloud.utils.exception.CloudRuntimeException: Unable to mount
>> 192.168.10.60:/volume1/cloudstack-dev/secondary at
>> /mnt/SecStorage/4683f710-43e8-359d-bc9a-041363aa77b9 due to mount.nfs:
>> parsing error on 'vers=‘ option
>> I’m not sure how to troubleshoot this issue. Do I have to specify the
>> version somewhere for NFS?
>> Thanks
>> On May 30, 2021, at 12:30 AM, Jeremy Hansen
>> <jer...@skidrow.la<mailto:jer...@skidrow.la>> wrote:
>> At the very end of the configuration wizard when it’s doing the Host vm
>> install, I get this error and I can’t get past it:
>> Something went wrong; please correct the following:
>> TypeError: Cannot read property 'value' of undefined
>> Thanks
>> -jeremy
>> On May 29, 2021, at 11:27 PM, Jeremy Hansen
>> <jer...@skidrow.la<mailto:jer...@skidrow.la>> wrote:
>> New to Cloudstack. I’m trying to get the Quickstart going.
>> It feels like an issue with secondary storage but I’m not quite sure how to
>> troubleshoot.
>> CentOS 8, kvm. Created a bridge per the quick install docs.
>> <Screen Shot 2021-05-29 at 11.23.42 PM.png>
>> I see no data for templates and isos. I did do the template install. The
>> secondary storage VM is running and connected:
>> <Screen Shot 2021-05-29 at 11.25.22 PM.png>
>> <Screen Shot 2021-05-29 at 11.26.23 PM.png>
>> <Screen Shot 2021-05-29 at 11.26.43 PM.png>
>> I attempted to upload an iso and it failed.
>> Also, how do I get back to the initial configuration wizard. I dismissed it
>> but I’m not sure how to get it back.
>> Thanks!
>> -jeremy
