On Thu, Jun 06, 2024 at 09:32:17AM +0200, [email protected] wrote: > From: Christian Ehrhardt <[email protected]> > > DPDK fixed counting of telemetry clients in 24.03 [1] which was also > backported to 23.11.1 [2]. Due to that the dpdk related openvswitch > tests now fail in the following cases: > 4: OVS-DPDK - ping vhost-user ports FAILED (system-dpdk.at:148) > 5: OVS-DPDK - ping vhost-user-client ports FAILED (system-dpdk.at:224) > 16: OVS-DPDK - MTU increase vport port FAILED (system-dpdk.at:609) > 17: OVS-DPDK - MTU decrease vport port FAILED (system-dpdk.at:651) > 20: OVS-DPDK - MTU upper bound vport port FAILED (system-dpdk.at:767) > 21: OVS-DPDK - MTU lower bound vport port FAILED (system-dpdk.at:809) > > This is due to a new error being logged under these conditions: > dpdk|ERR|TELEMETRY: Socket write base info to client failed > > This is okay to happen in the cases we set up in the DPDK related tests > for OVS and can be ignored, therefore it is added to the tolerated > messages in the m4 definition of OVS_DPDK_STOP_VSWITCHD. > > [1]: https://github.com/DPDK/dpdk/commit/e14bb5f1 > [2]: https://github.com/DPDK/dpdk-stable/commit/cbd1c165 > > Signed-off-by: Christian Ehrhardt <[email protected]> > --- > Changes since v1: > - adapt to grammar rules for the subject
Acked-by: Simon Horman <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
