Bug 1561299 - ovn could not add network device ovn-c203a5-0 to ofproto
Summary: ovn could not add network device ovn-c203a5-0 to ofproto
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-provider-ovn
Classification: oVirt
Component: driver
Version: 1.2.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.4
: ---
Assignee: Marcin Mirecki
QA Contact: Mor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-28 04:29 UTC by 曾浩
Modified: 2018-05-16 08:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-16 08:51:55 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+
ylavi: exception+


Attachments (Terms of Use)
ovirt ovn (198.15 KB, application/zip)
2018-03-28 09:00 UTC, 曾浩
no flags Details
logs (3.04 KB, application/zip)
2018-03-30 01:26 UTC, 曾浩
no flags Details

Description 曾浩 2018-03-28 04:29:58 UTC
Description of problem:

ovirt two node, use ovn, 
one is ok, the another error. 

error: "could not add network device ovn-c203a5-0 to ofproto (Address family not supported by protocol)"

Version-Release number of selected component (if applicable):

kernel version!!
Linux hptestenv70 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
package version!!
ovirt-node-ng-installer-ovirt-4.2-2018031106
Mar 11 06:06:28 Installed: 1:openvswitch-ovn-common-2.7.3-1.1fc27.el7.x86_64
Mar 11 06:06:57 Installed: 1:openvswitch-ovn-host-2.7.3-1.1fc27.el7.x86_64
Mar 11 06:12:14 Installed: ovirt-provider-ovn-driver-1.2.5-1.el7.centos.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yaniv Lavi 2018-03-28 07:37:46 UTC
Can you please attach logs (engine/ovn provider/host)?
Are you using IPv6?

Comment 2 曾浩 2018-03-28 09:00:22 UTC
Created attachment 1414091 [details]
ovirt ovn

Comment 3 曾浩 2018-03-28 09:01:19 UTC
(In reply to Yaniv Lavi from comment #1)
> Can you please attach logs (engine/ovn provider/host)?
> Are you using IPv6?

node:

21: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether b8:ca:3a:ec:fd:68 brd ff:ff:ff:ff:ff:ff
    inet 10.148.181.70/24 brd 10.148.181.255 scope global ovirtmgmt
       valid_lft forever preferred_lft forever
22: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether f6:50:47:77:8d:c0 brd ff:ff:ff:ff:ff:ff
50: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovirtmgmt state UNKNOWN qlen 1000
    link/ether fe:1a:4a:16:01:0b brd ff:ff:ff:ff:ff:ff
69: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 4a:c7:81:ae:24:14 brd ff:ff:ff:ff:ff:ff
70: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 5e:66:f8:3a:86:4d brd ff:ff:ff:ff:ff:ff

Comment 4 Marcin Mirecki 2018-03-29 08:37:34 UTC
As I understand the problem is that the ovn-controller on one of the hosts was not set up properly, with the ovn tunnel port not being added to br-int properly.

Can you please check the following:
- on each host run (to check the status of the ports connected to br-int):
    ovs-vsctl show
- on the engine host run (to check if the hosts registered with ovn central):
    ovn-sbctl show

Also please attach the following engine logs:
  /var/log/ovirt-engine/host-deploy/*
(with details about the vdsm-tool invocation that configures the ovn-controller)

Thanks,
Marcin

Comment 5 曾浩 2018-03-30 01:26:43 UTC
Created attachment 1414965 [details]
logs

Comment 6 Marcin Mirecki 2018-05-15 11:44:20 UTC
Based on information received from the ovs team, this problem could occur if the host on which this runs does not support  IPv6.
The Geneve tunnel require a kernel which supports IPv6.
Can you please check if this is the case?

Comment 7 曾浩 2018-05-16 01:53:56 UTC
env deleted。

Comment 8 Marcin Mirecki 2018-05-16 07:25:57 UTC
I am closing the bug for now.
Please reopen if the problem reappears.

Comment 9 曾浩 2018-05-16 08:51:55 UTC
(In reply to Marcin Mirecki from comment #8)
> I am closing the bug for now.
> Please reopen if the problem reappears.

TKS


Note You need to log in before you can comment on or make changes to this bug.