Ask Your Question
0

kolla multinode deployment ovs-system in DOWN state

asked 2016-11-15 02:11:33 -0500

Zohar gravatar image

openstack_release: "3.0.0"

Hi,

after deploying kolla multi-node (same 3 controls serve as network nodes) lost external connectivity from the controllers. eno1 - external, eno2 - internal

root@R630-24C-16M-500D-02:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether 14:18:77:5d:50:b7 brd ff:ff:ff:ff:ff:ff
    inet 172.30.70.113/23 brd 172.30.71.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::1618:77ff:fe5d:50b7/64 scope link
       valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 14:18:77:5d:50:b8 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.211/23 brd 10.10.11.255 scope global eno2
       valid_lft forever preferred_lft forever
    inet6 fe80::1618:77ff:fe5d:50b8/64 scope link
       valid_lft forever preferred_lft forever
4: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 14:18:77:5d:50:b9 brd ff:ff:ff:ff:ff:ff
5: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 14:18:77:5d:50:ba brd ff:ff:ff:ff:ff:ff
6: enp4s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:0f:53:3c:d3:50 brd ff:ff:ff:ff:ff:ff
7: enp4s0f1d1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:0f:53:3c:d3:51 brd ff:ff:ff:ff:ff:ff
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:99:a1:3f:3e brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever
9: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether da:f4:6a:80:83:83 brd ff:ff:ff:ff:ff:ff
10: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether 14:18:77:5d:50:b7 brd ff:ff:ff:ff:ff:ff
11: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether 1a:a0:e0:bf:31:46 brd ff:ff:ff:ff:ff:ff
12: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether 72:18:71:33:45:4a brd ff:ff:ff:ff:ff:ff

why is ovs-system DOWN?

Thanks, Zohar

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-12-12 21:05:32 -0500

EthanW gravatar image

I've found any bridge, vlan, or bonded interface that doesn't have an IP assigned to it won't be up when it is NetworkManager controlled. Add NM_CONTROLLED=no to your interface script.

edit flag offensive delete link more

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

Stats

Asked: 2016-11-15 02:11:33 -0500

Seen: 823 times

Last updated: Nov 15 '16