How to fix interface state of 'lo' of an L3 HA router namespace?
Issue
In some of our L3 HA router namespaces we observer the interface lo
reported as DOWN
:
[root@overcloud-controller-1 ~]# for ns in $(ip netns);do ip netns exec $ns ip l sh dev lo | grep -q DOWN && echo "Issue with name space $ns loopback down" ;done
Issue with name space qrouter-02a112bc-7b7b-416d-bb51-9781cb2faa11 loopback down
[root@overcloud-controller-1 ~]# ip netns exec qrouter-02a112bc-7b7b-416d-bb51-9781cb2faa11 ip a
1: lo: <loopback> mtu 65536 qdisc noop state DOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
61: qg-b797482d-76: <broadcast,multicast,up,lower_up> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:52:f0:45 brd ff:ff:ff:ff:ff:ff
69: ha-1046549e-b7: <broadcast,multicast,up,lower_up> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:08:11:f4 brd ff:ff:ff:ff:ff:ff
inet 169.254.192.2/18 brd 169.254.255.255 scope global ha-1046549e-b7
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe08:11f4/64 scope link
valid_lft forever preferred_lft forever
How can we bring up the lo
interface without interruption of other router namespaces?
Environment
- Red Hat OpenStack Platform 7.0
- L3 HA routers
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.