[
https://issues.apache.org/jira/browse/CLOUDSTACK-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599108#comment-13599108
]
Josh Zojonc commented on CLOUDSTACK-1264:
-----------------------------------------
I am also experiencing this problem. Neither of my system vms (sec storage or
console proxy) have default gateways.
root@v-1023-VM:~# ip route
x.x.x.x/25 dev eth2 proto kernel scope link src x.x.x.x
10.193.17.0/24 dev eth1 proto kernel scope link src 10.193.17.17
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.3.190
> System VM does not have default route.
> --------------------------------------
>
> Key: CLOUDSTACK-1264
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1264
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup, Network Devices, XenServer
> Affects Versions: 4.1.0
> Environment: Build #15, rhel 6.3
> Reporter: Parth Jagirdar
> Assignee: Jayapal Reddy
> Priority: Blocker
>
> While troubleshooting it was found that System VM doesnt have default route.
> Management sever logs that contains n/w info are attached. Which shows that
> N/W info including G/W being passed. (May be the script on VM failed to
> configure?)
> Other Hypervisor (VMWARE) didnt have this issue.
> This was confirmed on the setup mentioned in bug #1252. We were able to ping
> external world.
> https://issues.apache.org/jira/browse/CLOUDSTACK-1252
> Please contact if more info is needed.
--
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
