[ovs-dev] ovs 2.13.0 has lldp issues on 5.6.14 kernel

Ilya Maximets i.maximets at ovn.org
Fri Aug 21 12:46:34 UTC 2020


On 8/19/20 8:11 PM, Chuan Han wrote:
> Thanks. These patches fixed the build issue. 
> 
> I did not see the same lldp issue on 2.13.0. 
> 
> 2.13.1 is good. 
> 
> Does this mean we shall wait for the 2.13.1 debian package? or 2.14.0? Any suggestions?

I guess so.  However, I'm not sure when it will be available.
I do not know who works on these packages from the debian side.

> 
> Thanks.
> Chuan
> 
> On Wed, Aug 19, 2020 at 10:31 AM Ilya Maximets <i.maximets at ovn.org <mailto:i.maximets at ovn.org>> wrote:
> 
>     On 8/19/20 6:58 PM, Chuan Han wrote:
>     > Thanks Ilya for quick response.
>     >
>     > What is the best way of getting 2.13.1? I tried to build from source, but hit this issue. 
>     >
>     > openvswitch/vtep/vtep-ctl.8.in <http://vtep-ctl.8.in> <http://vtep-ctl.8.in>
>     > openvswitch/vtep/vtep-ctl.c
>     > # check we can get kernel module names
>     > /usr/bin/make -C datapath print-build-modules
>     > make[2]: Entering directory '/usr/local/google/home/chuanhan/project/ovs/datapath'
>     > openvswitch vport-geneve vport-gre vport-lisp vport-stt vport-vxlan
>     > make[2]: Leaving directory '/usr/local/google/home/chuanhan/project/ovs/datapath'
>     > # Prepare dkms.conf from the dkms.conf.in <http://dkms.conf.in> <http://dkms.conf.in> template
>     > sed "s/__VERSION__/2.13.1/g; s/__MODULES__/openvswitch vport-geneve vport-gre vport-lisp vport-stt vport-vxlan  /" debian/dkms.conf.in <http://dkms.conf.in> <http://dkms.conf.in> > debian/openvswitch-datapath-dkms/usr/src/openvswitch-2.13.1/dkms.conf
>     > # We don't need the debian folder in there, just upstream sources...
>     > rm -rf debian/openvswitch-datapath-dkms/usr/src/openvswitch-2.13.1/debian
>     > # We don't need the rhel stuff in there either
>     > rm -rf debian/openvswitch-datapath-dkms/usr/src/openvswitch-2.13.1/rhel
>     > # And we should also clean useless license files, which are already
>     > # described in our debian/copyright anyway.
>     > rm -f debian/openvswitch-datapath-dkms/usr/src/openvswitch-2.13.1/xenserver/LICENSE
>     > make[1]: Leaving directory '/usr/local/google/home/chuanhan/project/ovs'
>     >    dh_installdocs -O--parallel
>     > dh_installdocs: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>     >    dh_installchangelogs -O--parallel
>     > dh_installchangelogs: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>     >    debian/rules override_dh_installman
>     > make[1]: Entering directory '/usr/local/google/home/chuanhan/project/ovs'
>     > dh_installman --language=C
>     > dh_installman: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>     > dh_installman: error: Cannot find (any matches for) "utilities/ovs-appctl.8" (tried in .)
>     >
>     > dh_installman: error: Cannot find (any matches for) "utilities/ovs-ctl.8" (tried in .)
>     >
>     > dh_installman: error: Cannot find (any matches for) "utilities/ovs-l3ping.8" (tried in .)
>     >
>     > dh_installman: error: Aborting due to earlier error
>     > make[1]: *** [debian/rules:94: override_dh_installman] Error 255
>     > make[1]: Leaving directory '/usr/local/google/home/chuanhan/project/ovs'
>     > make: *** [debian/rules:25: binary] Error 2
>     >
>     > It might be because the following is missing.
>     >
>     > $ dpkg-checkbuilddeps
>     > dpkg-checkbuilddeps: error: Unmet build dependencies: python3-twisted-conch python3-zopeinterface
>     >
>     > Again, my kernel is 5.6. I only have python3-twisted and python3-zope.interface instead. 
>     >
>     > Are these two packages the culprit? Or, 2.13 and older versions cannot be built on 5.5+ kernel? Is there a way to skip building the kernel model? It seems that the building kernel model failed. 
>     >
>     > Please advise.
> 
>     Oh.  Unfortunately there is a known issue with 2.13.  Some patches are missing.
>     Related issue: https://github.com/openvswitch/ovs-issues/issues/194
> 
>     You could try clone the openvswitch repo, checkout branch-2.13 and execute
>     $ git cherry-pick c101cd417 3c18bb0fe fe175ac17
> 
>     So, you'll have following three commits applied:
>     * fe175ac17 2020-05-15 | debian: Add python3-sphinx to ovs build dependencies [Ansis Atteka]
>     * 3c18bb0fe 2020-05-14 | debian: Fix package dependencies [Roi Dayan]
>     * c101cd417 2020-05-13 | debian: Fix broken build after some man pages became generated from RST [Ansis Atteka]
> 
>     Alternatively, you could try to just modify the code in a way like these commits does.
> 
>     There are few incorrect dependencies and also manpage files moved around.
>     This is not related to kernel.  I hope, we will have these commits backported to 2.13 soon.
>     Sorry for inconvenience.
> 
> 
>     >
>     > Thanks.
>     > Chuan
>     >
>     > On Wed, Aug 19, 2020 at 9:35 AM Ilya Maximets <i.maximets at ovn.org <mailto:i.maximets at ovn.org> <mailto:i.maximets at ovn.org <mailto:i.maximets at ovn.org>>> wrote:
>     >
>     >     On 8/19/20 6:17 PM, Chuan Han via dev wrote:
>     >     > Hi, ovs dev,
>     >     >
>     >     > We recently hit a lldp issue, e.g., lldp functionality does not work
>     >     > reliably, when ovs was upgraded from 2.11.0 to 2.13.0 on kernel 5.6. I
>     >     > heard from other sources that to be compatible with kernel 5.5+, we need
>     >     > 2.14+. I upgraded ovs to 2.14, and it seems ovs lldp works fine now.
>     >     >
>     >     > Is this a known issue? Is this true that for kernel 5.5+, we need 2.14+
>     >     > ovs? I checked the debian tracker for ovs
>     >     > <https://tracker.debian.org/pkg/openvswitch>. I did not see ovs 2.14 there
>     >     > yet.
>     >
>     >     Hi.  Userspace components should work fine with any kernel.  You do need
>     >     2.14+ in case you want to build out-of-tree kernel module, but, I guess,
>     >     that is not what you want.
>     >
>     >     In case you have an issue with 2.13.0 and there is no issue with 2.14, I'd
>     >     suggest to try 2.13.1.  There were many bug fixes backported since 2.13.0.
>     >
>     >     Please, give it a try and reply if it works for you.  If not, you could
>     >     try to bisect branch-2.14 to find which commit actually fixes the issue
>     >     or give us more details to take a look and find a suitable fix.
>     >
>     >     Best regards, Ilya Maximets.
>     >
> 



More information about the dev mailing list