Bug 1774596 - ovs error: on vxlan_sys_4789 device failed: No such device
Summary: ovs error: on vxlan_sys_4789 device failed: No such device
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: openvswitch
Version: FDP 18.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Timothy Redaelli
QA Contact: liting
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-20 14:20 UTC by Miguel Angel Nieto
Modified: 2022-11-28 15:08 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-28 15:08:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1788978 0 None None None 2019-11-25 20:14:35 UTC
Red Hat Issue Tracker FD-355 0 None None None 2021-12-15 06:20:18 UTC
Red Hat Issue Tracker FD-356 0 None None None 2021-12-15 06:20:22 UTC

Description Miguel Angel Nieto 2019-11-20 14:20:33 UTC
Description of problem:

Testing FFU, i discovered these errors in ovs log file when I have osp 10 installed
2019-11-20T03:20:08.124Z|42950|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on vxlan_sys_4789 device failed: No such device
2019-11-20T03:20:08.139Z|42952|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on vxlan_sys_4789 device failed: No such device
2019-11-20T03:25:08.233Z|42956|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on vxlan_sys_4789 device failed: No such device
2019-11-20T03:25:08.237Z|42957|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on vxlan_sys_4789 device failed: No such device
2019-11-20T03:25:08.240Z|42958|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on vxlan_sys_4789 device failed: No such device
2019-11-20T03:25:08.244Z|42959|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on vxlan_sys_4789 device failed: No such device
2019-11-20T03:25:08.257Z|42960|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on vxlan_sys_4789 device failed: No such device

After executing ffu to osp13, I continue having these messages



Version-Release number of selected component (if applicable):
install osp10 with these templates
https://code.engineering.redhat.com/gerrit/gitweb?p=nfv-qe.git;a=tree;f=ospd-10-vxlan-dpdk-sriov-ctlplane-dataplane-bonding-hybrid;h=2b43c11678d828c8daf88de6f518263309d8fd89;hb=refs/heads/ci

Then execute ffu



How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Miguel Angel Nieto 2019-11-20 16:04:42 UTC
sos report
http://rhos-release.virt.bos.redhat.com/log/bz1774596/

Comment 2 Bernard Cafarelli 2019-11-21 15:55:16 UTC
Neutron does not create/handle these ports, this seems to be DPDK-specific

Comment 5 Chris Fields 2019-12-05 13:05:22 UTC
Miguel, I should have asked this before but do the symptoms in this bz match the launchpad bug? 

"vm of 2 compute nodes cannot communicate through vxlan network"

Need to know if the error message is the only observed issue or what other problem is this causing?  

thanks

CFields

Comment 6 Miguel Angel Nieto 2019-12-05 13:44:04 UTC
Hi, i didnt see any problem, only the log file. Communication through vxlan was ok

Comment 7 Gowrishankar Muthukrishnan 2020-04-29 09:30:15 UTC
(In reply to Miguel Angel Nieto from comment #6)
> Hi, i didnt see any problem, only the log file. Communication through vxlan
> was ok

One relevant fix which is available in later 2.11 rpms (not the one used in your deployment) is:
https://patchwork.ozlabs.org/project/openvswitch/patch/1554122243-125096-1-git-send-email-chrism@mellanox.com/#2151850

But not sure if we ever change default dst port, just for the reference here.


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