[
https://issues.apache.org/jira/browse/CLOUDSTACK-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663863#comment-13663863
]
ASF subversion and git services commented on CLOUDSTACK-2308:
-------------------------------------------------------------
Commit e31553aff827abd88e3dfa9b65bfb335e09fbd22 in branch refs/heads/master
from [~jayapal]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e31553a ]
CLOUDSTACK-2308 fixed adding route in vware for mgmt subnet
Signed-off-by: Abhinandan Prateek <aprat...@apache.org>
> [VPC] [VMware] Failed to bring up VPC router
> --------------------------------------------
>
> Key: CLOUDSTACK-2308
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2308
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Environment: commit 09af15035b9febe6f55e73a1389f950ab042564f
> Reporter: venkata swamybabu budumuru
> Assignee: Jayapal Reddy
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have an advanced zone with VMware
> 2. Try to create a VPC
> Observations :
> (i) Have seen errors like "Could not connect to 10.147.40.76 due to
> java.net.ConnectException: Connection timed out"
> (ii) When i checked "route -n" on the VPC router, couldn't find any route
> that makes the communication between mgmt server and router.
> (iii) found the following error during the cloud-early-config
> + '[' -n 10.147.59.0/24 -a -n 10.147.40.1 ']'
> + ip route add 10.147.59.0/24 via 10.147.40.1 dev eth1
> Cannot find device "eth1"
> + ip route delete default"
> (iv) attaching the log for cloud-early-config which was run using "set -x".
> (v) here is the route -n output at the time of issue
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 10.147.40.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
> (vi) ifconfig output at the time of issueroot@r-20-VM:~# ifconfig -a
> eth0 Link encap:Ethernet HWaddr 02:00:53:64:00:0c
> inet addr:10.147.40.76 Bcast:10.147.41.255 Mask:255.255.254.0
> inet6 addr: fe80::53ff:fe64:c/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3919 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1010 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:301242 (294.1 KiB) TX bytes:163172 (159.3 KiB)
> 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:10 errors:0 dropped:0 overruns:0 frame:0
> TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1318 (1.2 KiB) TX bytes:1318 (1.2 KiB)
> Attaching all the required logs along with db dump to the bug.
> Here is brief about my network info :
> Mgmt sever : 10.147.59.194/24
> mgmt network : 10.147.40.x/24
> public network : 10.147.44.x/24
--
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
