[
https://issues.apache.org/jira/browse/CLOUDSTACK-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511334#comment-13511334
]
John Burwell commented on CLOUDSTACK-590:
-----------------------------------------
The following Marvin configuration will create a network configuration that
reproduces this defect on a devcloud with two NICs -- eth0 (host-only,
192.168.56.15) and eth1 (NAT, dhcp):
{
"zones": [
{
"name": "zone00",
"physical_networks": [
{
"broadcastdomainrange": "Zone",
"name": "zone00-pn00",
"traffictypes": [
{
"typ": "Guest"
},
{
"typ": "Management"
}
],
"providers": [
{
"broadcastdomainrange": "ZONE",
"name": "VirtualRouter"
},
{
"broadcastdomainrange": "Pod",
"name": "SecurityGroupProvider"
}
]
}
],
"dns1": "8.8.8.8",
"securitygroupenabled": "true",
"networktype": "Basic",
"pods": [
{
"name": "zone00-pod00",
"startip": "192.168.56.100",
"endip": "192.168.56.149",
"netmask": "255.255.255.0",
"gateway": "192.168.56.1",
"guestIpRanges": [
{
"startip": "10.0.3.200",
"endip": "10.0.3.220",
"netmask": "255.255.255.0",
"gateway": "10.0.3.2"
}
],
"clusters": [
{
"clustername": "zone00-pod00-cluster00",
"hypervisor": "XenServer",
"hosts": [
{
"name": "192.168.56.15",
"username": "root",
"url": "http://192.168.56.15/";,
"password": "password"
}
],
"clustertype": "CloudManaged"
}
]
}
],
"internaldns1": "192.168.56.15",
"localstorageenabled": "true",
"secondaryStorages": [
{
"url": "nfs://192.168.56.15/opt/storage/secondary"
}
]
}
],
"logger": [
{
"name": "TestClient",
"file": "/tmp/testclient.log"
},
{
"name": "TestCase",
"file": "/tmp/testcase.log"
}
],
"globalConfig": [
{
"name": "expunge.workers",
"value": "3"
},
{
"name": "expunge.delay",
"value": "60"
},
{
"name": "expunge.interval",
"value": "60"
},
{
"name": "system.vm.use.local.storage",
"value": "true"
},
{
"name": "s3.enable",
"value": "true"
},
{
"name": "cpu.overprovisioning.factor",
"value": "30"
},
{
"name": "mem.overprovisioning.factor",
"value": "30"
},
{
"name": "storage.overprovisioning.factor",
"value": "30"
},
{
"name": "management.network.cidr",
"value": "192.168.56.0/24"
},
{
"name": "host",
"value": "192.168.56.15"
},
{
"name": "enable.ec2.api",
"value": "false"
},
{
"name": "enable.s3.api",
"value": "false"
}
],
"mgtSvr": [
{
"mgtSvrIp": "127.0.0.1",
"port": 8096
}
]
}
> Incorrect Network Gateways Assigned to System VMs
> -------------------------------------------------
>
> Key: CLOUDSTACK-590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-590
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Network Devices, Xen
> Affects Versions: 4.1.0
> Environment: Ubuntu 12.04.1, Xen 4.1 running on VirtualBox 4.2.4
> Reporter: John Burwell
> Priority: Critical
>
> When configuring a network with a DNS on a different network, CloudStack
> creates an incorrect route for system VMs. Using the following network
> configuration, a route between 10.0.3.2 and 192.168.56.1 is incorrectly
> created:
> * Management Network: 192.168.56.100-192.168.56.149 gw 192.168.56.1 dns
> 10.0.3.2
> * Guest Network: 10.0.3.200-10.0.3.220 gw 10.0.3.2 dns 10.0.3.2
> It appears that CloudStack assumes a route between 192.168.56.1 and 10.0.3.2
> based on the DNS configuration. This assumption is false, and not explicitly
> specified in the configuration. CloudStack should defer to the router to
> make the this topology function.
--
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
