[ovs-discuss] openvswitch not fault tolerant or contain failover mechanism

Amer Hwitat amer.hwaitat at gmail.com
Thu Jan 24 23:59:06 UTC 2019


I mean the configuration was for br-ex as follows:

TYPE=OVSBridge
DEVICE=br-ex
DEVICETYPE=ovs
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
ONBOOT=yes
IPADDR=192.168.43.110
PREFIX=24
GATEWAY=192.168.43.1
DNS=192.168.43.1
BOOTPROTO=static
NM_CONTROLLED=no
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
PROXY_METHOD=none
BROWSER_ONLY=no



On Fri, Jan 25, 2019 at 2:01 AM Amer Hwitat <amer.hwaitat at gmail.com> wrote:

> Hi,
>
> I have the following issue:
>
> [root at localhost neutron]# systemctl status network
> ● network.service - LSB: Bring up/down networking
>    Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
>    Active: active (exited) since Tue 2019-01-22 09:13:04 EST; 58min ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 10275 ExecStart=/etc/rc.d/init.d/network start (code=exited,
> status=0/SUCCESS)
>     Tasks: 0
>
> Jan 22 09:12:58 localhost.localdomain systemd[1]: Starting LSB: Bring
> up/down networking...
> Jan 22 09:12:59 localhost.localdomain network[10275]: Bringing up loopback
> interface:  [  OK  ]
> Jan 22 09:12:59 localhost.localdomain ovs-vsctl[10407]:
> ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --may-exist add-br br-ex
> Jan 22 09:13:04 localhost.localdomain network[10275]: Bringing up
> interface br-ex:  [  OK  ]
> Jan 22 09:13:04 localhost.localdomain ovs-vsctl[10573]:
> ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --if-exists del-port
> br-ex eno16777736 -- add-port...o16777736
> Jan 22 09:13:04 localhost.localdomain network[10275]: Bringing up
> interface eno16777736:  [  OK  ]
> Jan 22 09:13:04 localhost.localdomain systemd[1]: Started LSB: Bring
> up/down networking.
> Hint: Some lines were ellipsized, use -l to show in full.
> [root at localhost neutron]#
>
> casue by this configuration of eno16777736 interface on a VM:
> settings:
>
> HWADDR=00:0C:29:37:19:1F
> TYPE=OVSBridge
> DEVICE=br-ex
> DEVICETYPE=ovs
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=no
> UUID=c0addf73-98fe-464c-804a-b40110fd6157
> ONBOOT=yes
> IPADDR=192.168.43.110
> PREFIX=24
> GATEWAY=192.168.43.1
> DNS=192.168.43.1
> BOOTPROTO=static
> NM_CONTROLLED=no
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> IPV6_DEFROUTE=yes
> IPV6_FAILURE_FATAL=no
> PROXY_METHOD=none
> BROWSER_ONLY=no
>
> HWADDR=00:0C:29:37:19:1F
> TYPE=OVSPort
> DEVICE=eno16777736
> DEVICETYPE=ovs
> UUID=c0addf73-98fe-464c-804a-b40110fd6157
> OVS_BRIDGE=br-ex
> BOOTPROTO=none
> ONBOOT=yes
> PROMISC=yes
> PROXY_METHOD=none
> DEFROUTE=yes
> PEERDNS=yes
> PEERROUTES=yes
> NM_CONTROLLED=no
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> IPV6_DEFROUTE=yes
> IPV6_FAILURE_FATAL=no
> NAME=eno16777736
> PROXY_METHOD=none
> BROWSER_ONLY=no
>
> which causes this bug:
>
> [root at localhost log]#
> Message from syslogd at localhost at Jan 23 02:23:31 ...
>  kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
> [ovsdb-server:10088]
>
> which crashes the VM or Server CPU to may cause critical situation, and
> repair , rescue and restore to the server...
>
> mentioned in
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1666598
> https://bugs.launchpad.net/neutron/+bug/1811941
> https://access.redhat.com/support/cases/#/case/02293077
> https://postimg.cc/gallery/29c2o4ftu/
> https://imgur.com/a/X6bEPop
>
> by me ... if there is a mis-configuration from my side please reply with
> remedy solution please ...
>
> Best regards
> Amer Hwitat
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20190125/a3b3c014/attachment.html>


More information about the discuss mailing list