You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/12/01 10:08:00 UTC
[jira] [Commented] (CLOUDSTACK-10127) 4.9 / 4.10 KVM + openvswitch
+ vpc + static nat / secondary ip on eth2?
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274196#comment-16274196 ]
ASF GitHub Bot commented on CLOUDSTACK-10127:
---------------------------------------------
rhtyd commented on issue #2304: CLOUDSTACK-10127: KVM + Ovs: Incorrect devId on static nat
URL: https://github.com/apache/cloudstack/pull/2304#issuecomment-348454888
@fmaximus we've done a couple of rounds of regression tests, can you check the failures? Alternatively, re-open this for master?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> 4.9 / 4.10 KVM + openvswitch + vpc + static nat / secondary ip on eth2?
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10127
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10127
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: VPC
> Affects Versions: 4.7.0, 4.8.0, 4.9.0, 4.10.0.0
> Environment: CentOS 7.4.1708 + KVM + OpenvSwitch 2.3-2.8
> Reporter: Sven Vogel
> Assignee: Frank Maximus
> Priority: Critical
>
> We have the following Problem.
> 1. KVM
> 2. Bridges
> bond with two interfaces and trunk (0,129,180,100-1500) to cloudbr0
> Cloudbr0 (0 - guest network)
> Fakebridge pub129 (public network)
> Fakebridge sto180 (secondary storage network)
> Fakebridge mgmt0 (management)
> If I have a vpc all things work until I add a secondary ip and add a static nat.
> The following will happen, first address will be on the the correct interface 146.0.122.134/26 but static nat will be on the false network.
> Its on the eth2…
> {{ root@r-29-VM:~# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
> link/ether 0e:00:a9:fe:03:81 brd ff:ff:ff:ff:ff:ff
> inet 169.254.3.129/16 brd 169.254.255.255 scope global eth0
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
> link/ether 1e:00:2c:00:00:68 brd ff:ff:ff:ff:ff:ff
> inet 146.0.122.134/26 brd 146.0.122.191 scope global eth1
> 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
> link/ether 02:00:57:07:00:0c brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.254/24 brd 192.168.1.255 scope global eth2
> inet 146.0.122.135/26 brd 146.0.122.191 scope global eth2}}
> Normally I think the secondary ip should be on signed to eth1 not eth2!
> It sets my ip on the guest network vlan range on my cloudbr0 but it should be pub129. vnet6 has 1353 guest tag and not the public tag.
> [root@kvm01 ~]# ovs-vsctl list-br
> cloud0
> cloudbr0
> mgmt0
> pub129
> sto180
> [root@kvm01 ~]# virsh domiflist r-29-VM
> Interface Type Source Model MAC
> -------------------------------------------------------
> vnet4 bridge cloud0 virtio 0e:00:a9:fe:03:81
> vnet5 bridge pub129 virtio 1e:00:2c:00:00:68
> vnet6 bridge cloudbr0 virtio 02:00:57:07:00:0c
> Bridge "cloud0"
> Port "vnet4"
> Interface "vnet4"
> Port "vnet5"
> tag: 129
> Interface "vnet5"
> Port "vnet6"
> tag: 1353
> Interface "vnet6"
> root@r-29-VM:~# cat /etc/cloudstack/ips.json {
> "eth0": [
> {
> "add": true,
> "broadcast": "169.254.255.255",
> "cidr": "169.254.3.129/16",
> "device": "eth0",
> "gateway": "None",
> "netmask": "255.255.0.0",
> "network": "169.254.0.0/16",
> "nic_dev_id": "0",
> "nw_type": "control",
> "one_to_one_nat": false,
> "public_ip": "169.254.3.129",
> "size": "16",
> "source_nat": false
> }
> ],
> "eth1": [
> {
> "add": true,
> "broadcast": "146.0.122.191",
> "cidr": "146.0.122.134/26",
> "device": "eth1",
> "first_i_p": true,
> "gateway": "146.0.122.130",
> "netmask": "255.255.255.192",
> "network": "146.0.122.128/26",
> "new_nic": false,
> "nic_dev_id": 1,
> "nw_type": "public",
> "one_to_one_nat": false,
> "public_ip": "146.0.122.134",
> "size": "26",
> "source_nat": true,
> "vif_mac_address": "1e:00:2c:00:00:68"
> }
> ],
> "eth2": [
> {
> "add": true,
> "broadcast": "146.0.122.191",
> "cidr": "146.0.122.135/26",
> "device": "eth2",
> "first_i_p": true,
> "gateway": "146.0.122.130",
> "netmask": "255.255.255.192",
> "network": "146.0.122.128/26",
> "new_nic": false,
> "nic_dev_id": 2,
> "nw_type": "public",
> "one_to_one_nat": true,
> "public_ip": "146.0.122.135",
> "size": "26",
> "source_nat": true,
> "vif_mac_address": "1e:00:2c:00:00:68"
> },
> {
> "add": false,
> "broadcast": "146.0.122.191",
> "cidr": "146.0.122.136/26",
> "device": "eth2",
> "first_i_p": true,
> "gateway": "146.0.122.130",
> "netmask": "255.255.255.192",
> "network": "146.0.122.128/26",
> "new_nic": false,
> "nic_dev_id": 2,
> "nw_type": "public",
> "one_to_one_nat": true,
> "public_ip": "146.0.122.136",
> "size": "26",
> "source_nat": true,
> "vif_mac_address": "1e:00:2c:00:00:68"
> },
> {
> "add": true,
> "broadcast": "192.168.1.255",
> "cidr": "192.168.1.254/24",
> "device": "eth2",
> "gateway": "192.168.1.254",
> "netmask": "255.255.255.0",
> "network": "192.168.1.0/24",
> "nic_dev_id": "2",
> "nw_type": "guest",
> "one_to_one_nat": false,
> "public_ip": "192.168.1.254",
> "size": "24",
> "source_nat": false
> }
> ],
> "id": "ips"
> }
> Frank Maximus from Nuage analysed the problem.
> {quote}
> That seems to be a bug in the lookup of the device number, in case of openvswitch.
> The config clearly sets device to eth2, while it should be eth1.
> More specifically:
> in LibvirtComputingResource.prepareNetworkElementCommand()
> The broadcastUriToNicNum map is filled depending on the VR nics.
> In openvswitch the guest bridge is used as is, so it overwrites the mapping of public.
> This was not an issue until 4.6 as then VR was using the macaddress to do lookup, while now it is using the device number.
> Kind Regards,
> Frank{quote}
> I hope anyone can fix that fastly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)