"Power, Ciara" <ciara.po...@intel.com> writes: > + Patrick > > > > From: Power, Ciara > Sent: Tuesday, March 5, 2024 10:05 AM > To: Sivaramakrishnan, VenkatX <venkatx.sivaramakrish...@intel.com>; Akhil > Goyal <gak...@marvell.com> > Cc: Ji, Kai <kai...@intel.com>; Aaron Conole <acon...@redhat.com> > Subject: RE: reg. https://patches.dpdk.org/project/dpdk/list/?series=31200 - > patch result > > > > Hi folks, > > > > Had a quick look, I can also see this: > > crypto/ipsec_mb: IPSec_MB version >= 1.4.0 is required, found version 1.2.0
This version of ipsec_mb is less than 1 year old. Did this pass any other CI testing? I would be surprised if it did - I'm not sure any downstream environments that would be using it already. > I guess the installed PMD .so file isn’t created because they are not > compiled in, due to the minimum version on > environment not meeting the new requirements. I don't see any such new requirements anywhere on the crypto tree. The only change I know about was for QAT to try and default to IPSec_MB 1.4, but it is supposed to fall back to OpenSSL if that is unavailable. Did this change? > CC’ing Aaron, who might know about upgrading that environment to ipsec-mb > v1.4. > > > > Thanks, > > Ciara > > > > From: Sivaramakrishnan, VenkatX <venkatx.sivaramakrish...@intel.com> > Sent: Monday, March 4, 2024 10:45 AM > To: Akhil Goyal <gak...@marvell.com> > Cc: Ji, Kai <kai...@intel.com>; Power, Ciara <ciara.po...@intel.com> > Subject: reg. https://patches.dpdk.org/project/dpdk/list/?series=31200 - > patch result > > > > Hi Akhil, > > > > I would like to provide details of the failures > > > > > > * > > > > > > Failures details: > > ============ > > "Build and test" failed for "librte_crypto_ipsec_mb.so". > > doc: remove outdated version details · ovsrobot/dpdk@f40ab34 (github.com) > > Error: cannot find librte_crypto_ipsec_mb.so.24.0 in install > > > > Looks like, “ipsec mb” was not installed on the server. > > > > However, the patch changes are related to the Doc update. Hope that this will > not impact patch merging > > > > Thank you. > > > > Best Regards, > > Venkat.
