Ask Your Question
0

[kolla] all bridge interfaces are down

asked 2019-04-13 23:52:31 -0500

vblando gravatar image

Kolla-ansible 7.1.0 on CentOS 7, Rocky release

1st NIC = bond0, with public IP

2nd NIC = enp1s0f1, no IP

globals.yml
network_interface: "bond0"
neutron_external_interface: "enp1s0f1"
kolla_internal_vip_address: "<public_IP"
enable_haproxy: "no"

[root@openstack-controller1 kolla]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp1s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 50:6b:4b:09:15:14 brd ff:ff:ff:ff:ff:ff
3: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP qlen 1000
    link/ether 50:6b:4b:09:15:15 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::526b:4bff:fe09:1515/64 scope link
       valid_lft forever preferred_lft forever
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 50:6b:4b:09:15:14 brd ff:ff:ff:ff:ff:ff
    inet <public_IP>/31 brd 255.255.255.255 scope global bond0
       valid_lft forever preferred_lft forever
    inet 10.64.26.131/31 brd 255.255.255.255 scope global bond0:0
       valid_lft forever preferred_lft forever
    inet6 2604:1380:3000:2d00::3/127 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::526b:4bff:fe09:1514/64 scope link
       valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
    link/ether 02:42:7f:81:3e:e0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever
6: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 02:fd:7d:e3:23:3b brd ff:ff:ff:ff:ff:ff
7: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 50:6b:4b:09:15:15 brd ff:ff:ff:ff:ff:ff
8: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 4a:0b:79:a2:5a:43 brd ff:ff:ff:ff:ff:ff
9: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether a2:fb:30:b8:e5:4d brd ff:ff:ff:ff:ff:ff
13: vxlan_sys_4789: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN qlen 1000
    link/ether 6a:82:0f:b1:d8:d4 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6882:fff:feb1:d8d4/64 scope link
       valid_lft forever preferred_lft forever
[root@openstack-controller1 kolla]#
edit retag flag offensive close merge delete

Comments

Could you share output of docker exec openvswitch_vswitchd ovs-vsctl show in both controller and compute hosts?

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2019-04-15 02:06:55 -0500 )edit
vblando gravatar imagevblando ( 2019-04-15 03:23:24 -0500 )edit

So, compute->controller tunnel is working at first glance, gateway is reachable so q-router is acting properly. Can you try to ping google from the q-router? Could be a NAT issue?

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2019-04-15 03:42:13 -0500 )edit

it can't ping out from the q-router http://paste.openstack.org/raw/dsUKWt...

vblando gravatar imagevblando ( 2019-04-15 04:02:48 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2019-04-14 22:43:12 -0500

vblando gravatar image

Additional Update 1. The instance can ping it's gateway (the controller) but beyond that, there's nothing. C:\fakepath\2019-04-15 11_42_08-Window.png

edit flag offensive delete link more

Comments

complete ping tests 1. VM to VM using the private IP = success 2. VM to VM using the floating IP = success 3. VM to VM router = success 4. Controller/Compute to VM = failed

vblando gravatar imagevblando ( 2019-04-17 11:22:52 -0500 )edit
0

answered 2019-04-14 04:56:00 -0500

This should not be a problem - OVS bridges typically show as DOWN, but are still able to forward packets.

edit flag offensive delete link more

Comments

launched cirros but it cannot ping out

vblando gravatar imagevblando ( 2019-04-14 06:01:32 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-04-13 23:52:31 -0500

Seen: 21 times

Last updated: Apr 14