On 3/25/22 12:11, Vladislav Odintsov wrote:
> Hi,
> 
> I’m trying to build OVS v2.17.0 against CentOS 7.5 and 7.8.
> make rpm-fedora command runs successfully, but when it is called with check, 
> very many tests are failed.
> 
> make rpm-fedora RPMBUILD_OPT="--with check"
> 
> Most of tests fail like this:
> 
> 2392. packet-type-aware.at:515: testing ptap - check decap() prerequisits ...
> ./packet-type-aware.at:516: ovsdb-tool create conf.db 
> $abs_top_srcdir/vswitchd/vswitch.ovsschema
> ./packet-type-aware.at:516: ovsdb-server --detach --no-chdir --pidfile 
> --log-file --remote=punix:$OVS_RUNDIR/db.sock
> stderr:
> 2022-03-25T10:10:44Z|00001|vlog|INFO|opened log file 
> /home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/2392/ovsdb-server.log
> ./packet-type-aware.at:516: sed < stderr '
> /vlog|INFO|opened log file/d
> /ovsdb_server|INFO|ovsdb-server (Open vSwitch)/d'
> ./packet-type-aware.at:516: ovs-vsctl --no-wait init
> ./packet-type-aware.at:516: ovs-vswitchd --enable-dummy --disable-system 
> --disable-system-route  --detach --no-chdir --pidfile --log-file -vvconn 
> -vofproto_dpif -vunixctl
> stderr:
> 2022-03-25T10:10:44Z|00001|vlog|INFO|opened log file 
> /home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/2392/ovs-vswitchd.log
> 2022-03-25T10:10:44Z|00002|ovs_numa|INFO|Discovered 2 CPU cores on NUMA node 0
> 2022-03-25T10:10:44Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 2 CPU 
> cores
> 2022-03-25T10:10:44Z|00004|netlink_socket|WARN|setting extended ack support 
> failed (Protocol not available)
> 2022-03-25T10:10:44Z|00005|reconnect|INFO|unix:/home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/2392/db.sock:
>  connecting...
> 2022-03-25T10:10:44Z|00006|netlink_socket|WARN|setting extended ack support 
> failed (Protocol not available)
> 2022-03-25T10:10:44Z|00007|netlink_socket|INFO|netlink: could not enable 
> listening to all nsid (Operation not permitted)
> 2022-03-25T10:10:44Z|00008|reconnect|INFO|unix:/home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/2392/db.sock:
>  connected
> 2022-03-25T10:10:44Z|00009|netlink_socket|WARN|setting extended ack support 
> failed (Protocol not available)
> 2022-03-25T10:10:44Z|00010|netlink_socket|WARN|setting extended ack support 
> failed (Protocol not available)
> ./packet-type-aware.at:516: sed < stderr '
> /ovs_numa|INFO|Discovered /d
> /vlog|INFO|opened log file/d
> /vswitchd|INFO|ovs-vswitchd (Open vSwitch)/d
> /reconnect|INFO|/d
> /dpif_netlink|INFO|Generic Netlink family .ovs_datapath. does not exist/d
> /ofproto|INFO|using datapath ID/d
> /netdev_linux|INFO|.*device has unknown hardware address family/d
> /ofproto|INFO|datapath ID changed to fedcba9876543210/d
> /dpdk|INFO|DPDK Disabled - Use other_config:dpdk-init to enable/d
> /netlink_socket|INFO|netlink: could not enable listening to all nsid/d
> /probe tc:/d
> /tc: Using policy/d'
> --- /dev/null 2022-03-25 12:26:57.604000000 +0300
> +++ 
> /home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/at-groups/2392/stdout
>   2022-03-25 13:10:44.091016031 +0300
> @@ -0,0 +1,4 @@
> +2022-03-25T10:10:44Z|00004|netlink_socket|WARN|setting extended ack support 
> failed (Protocol not available)
> +2022-03-25T10:10:44Z|00006|netlink_socket|WARN|setting extended ack support 
> failed (Protocol not available)
> +2022-03-25T10:10:44Z|00009|netlink_socket|WARN|setting extended ack support 
> failed (Protocol not available)
> +2022-03-25T10:10:44Z|00010|netlink_socket|WARN|setting extended ack support 
> failed (Protocol not available)
> ovsdb-server.log:
>> 2022-03-25T10:10:44.033Z|00001|vlog|INFO|opened log file 
>> /home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/2392/ovsdb-server.log
>> 2022-03-25T10:10:44.037Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 
>> 2.17.0
> ovs-vswitchd.log:
>> 2022-03-25T10:10:44.077Z|00001|vlog|INFO|opened log file 
>> /home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/2392/ovs-vswitchd.log
>> 2022-03-25T10:10:44.079Z|00002|ovs_numa|INFO|Discovered 2 CPU cores on NUMA 
>> node 0
>> 2022-03-25T10:10:44.079Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 2 
>> CPU cores
>> 2022-03-25T10:10:44.079Z|00004|netlink_socket|WARN|setting extended ack 
>> support failed (Protocol not available)
>> 2022-03-25T10:10:44.079Z|00005|reconnect|INFO|unix:/home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/2392/db.sock:
>>  connecting...
>> 2022-03-25T10:10:44.079Z|00006|netlink_socket|WARN|setting extended ack 
>> support failed (Protocol not available)
>> 2022-03-25T10:10:44.079Z|00007|netlink_socket|INFO|netlink: could not enable 
>> listening to all nsid (Operation not permitted)
>> 2022-03-25T10:10:44.079Z|00008|reconnect|INFO|unix:/home/centos/rpmbuild/BUILD/openvswitch-2.17.0/tests/testsuite.dir/2392/db.sock:
>>  connected
>> 2022-03-25T10:10:44.081Z|00009|netlink_socket|WARN|setting extended ack 
>> support failed (Protocol not available)
>> 2022-03-25T10:10:44.081Z|00010|netlink_socket|WARN|setting extended ack 
>> support failed (Protocol not available)
>> 2022-03-25T10:10:44.082Z|00011|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.17.0
> 2392. packet-type-aware.at:515: 2392. ptap - check decap() prerequisits 
> (packet-type-aware.at:515): FAILED (packet-type-aware.at:516)
> 
> 
> This is a regression from v2.16.2, since on that version everything builds 
> and tests well — without any errors.
> Is there some breaking change and OVS 2.17 now is not compatible with CentOS 
> 7, or could be some configuration error on my build machine?

Hi,

The tests are failing due to a warning you see in the log.
In general, the warning is harmless and can be ignored, but
unfortunately it fails the test.  There is a patch to fix
that:
  
https://github.com/openvswitch/ovs/commit/812164adefc716dd35c50c2101e8e60a15167635

It's on branch-2.17, but we had no stable releases on that
branch yet.  I'm planning to release v2.17.1 next week or
the week after.

Best regards, Ilya Maximets.
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to