VM connected to two different networks

Bug #1557412 reported by Shlomo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DragonFlow
Invalid
High
vikas choudhary

Bug Description

A VM that connected to two networks, will be accessible only from single IP instead of from both IP addresses.

Below is a print using df-db tool of a VM that attached to two different networks:

Table = lport , Key = e9f1ee80-1976-4425-8af4-26fee8d7e906
------------------------------------------------------------
{"parent_name": null, "macs": ["fa:16:3e:fa:c1:60"], "name": "e9f1ee80-1976-4425-8af4-26fee8d7e906", "lswitch": "0b0dc7c5-57c4-4605-b1cd-defa916c9c2f", "port_security": ["fa:16:3e:fa:c1:60"], "enabled": true, "topic": "b04934ec80fa44058d95ae97150e7cb1", "ips": ["10.0.1.6"], "device_owner": "compute:dfstack", "chassis": "dfstack", "sgids": null, "tunnel_key": 19, "external_ids": {"neutron:port_name": ""}, "tag": null}

Table = lport , Key = 3077a0a5-0c00-4f9f-a3aa-0c9e64bb22d8
------------------------------------------------------------
{"parent_name": null, "macs": ["fa:16:3e:11:cd:9a"], "name": "3077a0a5-0c00-4f9f-a3aa-0c9e64bb22d8", "lswitch": "b5ca3879-36a9-462f-abeb-bb1e05e39bd6", "port_security": ["fa:16:3e:11:cd:9a"], "enabled": true, "topic": "b04934ec80fa44058d95ae97150e7cb1", "ips": ["192.168.0.6"], "device_owner": "compute:dfstack", "chassis": "dfstack", "sgids": null, "tunnel_key": 18, "external_ids": {"neutron:port_name": ""}, "tag": null}

Yuli (stremovsky)
Changed in dragonflow:
importance: Undecided → High
Gal Sagie (gal-sagie)
Changed in dragonflow:
assignee: nobody → Gal Sagie (gal-sagie)
Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

Hi Gal,

Can i look into this bug?

Changed in dragonflow:
assignee: Gal Sagie (gal-sagie) → vikas choudhary (choudharyvikas16)
status: New → In Progress
Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

This does not seem to be a valid bug. It is related to instance image setting.

I tested with cirros image. By default only one interface was enabled in "/etc/network/interfaces", so dhcp request was being sent for this single interface only. Enabled another interface also by adding lines in "/etc/network/interfaces" and rebooted vm, both interface ips were working.

Following are the details from ovs. In table 11, it can be seen that dhcp request is being sent for both interfaces:

apabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
 1(patch-int): addr:5e:53:af:e8:bc:d5
     config: 0
     state: 0
     speed: 0 Mbps now, 0 Mbps max
 11(qr-1d4ab656-be): addr:00:00:00:00:00:00
     config: PORT_DOWN
     state: LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
 12(qr-e8d55278-21): addr:00:00:00:00:00:00
     config: PORT_DOWN
     state: LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
 13(tap9a4918a8-09): addr:fe:16:3e:c9:e9:3d
     config: 0
     state: 0
     current: 10MB-FD COPPER
     speed: 10 Mbps now, 0 Mbps max
 14(tap10e267fd-42): addr:fe:16:3e:35:ca:41
     config: 0
     state: 0
     current: 10MB-FD COPPER
     speed: 10 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:9a:9a:55:49:91:43
     config: PORT_DOWN
     state: LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
root@PRINHYLTPHP0400:/home/vikasc/docker/docker# ovs-ofctl dump-flows table=11
ovs-ofctl: table=11 is not a bridge or a socket
root@PRINHYLTPHP0400:/home/vikasc/docker/docker# ovs-ofctl dump-flows br-int table=11
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=1086.044s, table=11, n_packets=6, n_bytes=2046, idle_age=419, priority=100,in_port=13 actions=load:0x16->OXM_OF_METADATA[],CONTROLLER:65535
 cookie=0x0, duration=1085.916s, table=11, n_packets=2, n_bytes=682, idle_age=418, priority=100,in_port=14 actions=load:0x17->OXM_OF_METADATA[],CONTROLLER:65535
 cookie=0x0, duration=21692.975s, table=11, n_packets=0, n_bytes=0, idle_age=65534, priority=1 actions=resubmit(,17)

Changed in dragonflow:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.