[
https://issues.apache.org/jira/browse/CLOUDSTACK-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657118#comment-13657118
]
John Burwell commented on CLOUDSTACK-2479:
------------------------------------------
[[email protected]] I just tried the systemvm target on this build
based on the instructions in INSTALL.md. Previously, the SSVMs worked with a
simple mvn clean install -P developer. For 4.1.0, what is the correct build
process to get a working SSVM image?
> No Connectivity Xen SSVM
> -------------------------
>
> Key: CLOUDSTACK-2479
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2479
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.1.0
> Environment: devcloud
> Reporter: John Burwell
> Priority: Blocker
>
> On devcloud/Xen, the SSVM is being successfully created (verified through
> both CloudStack and Xen) and it responds to pings at its link-local address.
> However, the management server is unable to connect to the agent and attempts
> to SSH to the the link-local address (i.e. ssh -p 3392 -i ~/.ssh/id_rsa.cloud
> <link-local address>) fail. An nmap of the public interface reports that
> ports 80 and 443 are open while an namp reports that no ports are open on the
> private or link-local interfaces.
> The zone is configured with basic networking, and the following networks:
> * Management
> - Gateway: 192.168.56.1
> - IP Range: 192.168.56.100-192.168.56.149
> - Xen Traffic Label: xenbr0
> * Guest
> - Gateway: 10.0.3.2
> - IP Range: 10.0.3.200-10.0.3.220
> - Xen Traffic Label: xenbr1
> The following is the Xen pif list from the host depicting the mapping of the
> traffic labels to physical interfaces:
> root@zone1:~# xe pif-list
> uuid ( RO) : 207413c9-5058-7a40-6c96-2dab21057f30
> device ( RO): eth1
> currently-attached ( RO): true
> VLAN ( RO): -1
> network-uuid ( RO): 1679ddb1-5a21-b827-ab07-c16275d5ce72
> uuid ( RO) : c0274787-e768-506f-3191-f0ac17b0c72b
> device ( RO): eth0
> currently-attached ( RO): true
> VLAN ( RO): -1
> network-uuid ( RO): 8ee927b1-a35d-ac10-4471-d7a6a475839a
> The following is a listing of the Xen vifs for the SSVM:
> root@zone1:~# xe vm-vif-list vm=c72614c4-dc28-b3c4-3400-1a34db81f187
> uuid ( RO) : 741fe852-b9e4-4b49-cfa9-c7b09fc8cbf6
> vm-name-label ( RO): s-8-VM
> device ( RO): 3
> MAC ( RO): 06:74:62:00:00:2f
> network-uuid ( RO): 8ee927b1-a35d-ac10-4471-d7a6a475839a
> network-name-label ( RO): xenbr0
> uuid ( RO) : 8460116b-8f25-97c1-0178-2a25282f3359
> vm-name-label ( RO): s-8-VM
> device ( RO): 1
> MAC ( RO): 06:12:3a:00:00:07
> network-uuid ( RO): 8ee927b1-a35d-ac10-4471-d7a6a475839a
> network-name-label ( RO): xenbr0
> uuid ( RO) : 342077d6-44cc-2ee9-a733-1cac9138bf5c
> vm-name-label ( RO): s-8-VM
> device ( RO): 0
> MAC ( RO): 0e:00:a9:fe:02:a5
> network-uuid ( RO): c67782a0-ea0e-8d50-ad09-9f3fff8a4ca1
> network-name-label ( RO): cloud_link_local_network
> uuid ( RO) : 9880bf5a-a66a-1d3f-65b5-493b15a8dec6
> vm-name-label ( RO): s-8-VM
> device ( RO): 2
> MAC ( RO): 06:83:9a:00:00:35
> network-uuid ( RO): 1679ddb1-5a21-b827-ab07-c16275d5ce72
> network-name-label ( RO): xenbr1
> Finally, the following is the ifconfig for the host itself:
> root@zone1:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 08:00:27:7e:74:9c
> inet6 addr: fe80::a00:27ff:fe7e:749c/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1418 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2853 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:207856 (207.8 KB) TX bytes:187744 (187.7 KB)
> eth1 Link encap:Ethernet HWaddr 08:00:27:df:00:00
> inet6 addr: fe80::a00:27ff:fedf:0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1081755 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2012200 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:409565427 (409.5 MB) TX bytes:2742512504 (2.7 GB)
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:1021408 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1021408 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2476556022 (2.4 GB) TX bytes:2476556022 (2.4 GB)
> vif17.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1
> RX packets:14 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2065 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:32
> RX bytes:764 (764.0 B) TX bytes:120310 (120.3 KB)
> vif17.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1
> RX packets:2689 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4698 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:32
> RX bytes:319908 (319.9 KB) TX bytes:547552 (547.5 KB)
> vif17.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1
> RX packets:52 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2099 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:32
> RX bytes:3592 (3.5 KB) TX bytes:124732 (124.7 KB)
> vif17.3 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:139 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:32
> RX bytes:0 (0.0 B) TX bytes:21093 (21.0 KB)
> vif4.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1
> RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> TX packets:312 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:32
> RX bytes:292 (292.0 B) TX bytes:18412 (18.4 KB)
> vif4.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1
> RX packets:1895 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1347 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:32
> RX bytes:102212 (102.2 KB) TX bytes:156194 (156.1 KB)
> vif4.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1
> RX packets:27 errors:0 dropped:0 overruns:0 frame:0
> TX packets:948 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:32
> RX bytes:756 (756.0 B) TX bytes:132252 (132.2 KB)
> xapi0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
> inet addr:169.254.0.1 Bcast:169.254.255.255 Mask:255.255.0.0
> inet6 addr: fe80::a087:27ff:feb7:9da7/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:83 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4319 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4440 (4.4 KB) TX bytes:253366 (253.3 KB)
> xenbr0 Link encap:Ethernet HWaddr 08:00:27:7e:74:9c
> inet addr:192.168.56.15 Bcast:192.168.56.255 Mask:255.255.255.0
> inet6 addr: fe80::a00:27ff:fe7e:749c/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:158084 errors:0 dropped:0 overruns:0 frame:0
> TX packets:151863 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:10473926 (10.4 MB) TX bytes:6337801241 (6.3 GB)
> xenbr1 Link encap:Ethernet HWaddr 08:00:27:df:00:00
> inet addr:10.0.3.15 Bcast:10.0.3.255 Mask:255.255.255.0
> inet6 addr: fe80::a00:27ff:fedf:0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:529173 errors:0 dropped:0 overruns:0 frame:0
> TX packets:286709 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:368500622 (368.5 MB) TX bytes:45967489 (45.9 MB)
> I encountered this issue when I pulled a fresh copy of the 4.1 branch, and
> built it using the following command:
> mvn -P developer,systemvm clean install
> I also cleared my database, and rebuilt using the following command:
> mvn -P developer -pl developer -Ddeploydb
> Finally, I defined using a known-good Marvin configuration for which JIRA
> provides no way to attach. However, I would happy to provide it upon request.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
