unable to ping instances

Bug #1769135 reported by Hanbae Seo
This bug report is a duplicate of:  Bug #1769136: unable to ping instances. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-kubernetes
New
Undecided
Unassigned

Bug Description

I deployed Kolla-Kubernetes on multi-node, but can't ping private IP of instance.
OVS information is below.

in network-node
```
()[root@network /]$ ovs-vsctl show
987956ec-393e-476f-ae86-0801dd2b1b2d
    Manager "ptcp:6640:0.0.0.0"
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap885f193a-3d"
            tag: 1
            Interface "tap885f193a-3d"
                type: internal
        Port "qr-75b7ea85-ee"
            tag: 1
            Interface "qr-75b7ea85-ee"
                type: internal
        Port "qg-4f4bde25-a9"
            tag: 2
            Interface "qg-4f4bde25-a9"
                type: internal
    Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth1"
            Interface "eth1"
    Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "vxlan-ac1e0153"
            Interface "vxlan-ac1e0153"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="172.30.1.82", out_key=flow, remote_ip="172.30.1.83"}

```

in compute-node
```
()[root@compute /]$ ovs-vsctl show
f06acf65-2f1a-43f2-acfe-b0b3eac2ad89
    Manager "ptcp:6640:0.0.0.0"
    Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth1"
            Interface "eth1"
    Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port "vxlan-ac1e0152"
            Interface "vxlan-ac1e0152"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="172.30.1.83", out_key=flow, remote_ip="172.30.1.82"}
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "qvo699b7638-e3"
            tag: 1
            Interface "qvo699b7638-e3"
        Port br-int
            Interface br-int
                type: internal
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
```

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.