Add QUARKUS-4612 workaround to nosql/infinispan

quarkus-qe / quarkus-test-suite

16 stars 34 forks source link

Add QUARKUS-4612 workaround to nosql/infinispan #2094

Closed mocenas closed 1 month ago

mocenas commented 1 month ago

Summary

https://issues.redhat.com/browse/QUARKUS-4612 causes nosql/infinispan module to fail on FIPS and mandrel. Add workaround for that

Please select the relevant options.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] Dependency update
[ ] Refactoring
[ ] Backport
[ ] New scenario (non-breaking change which adds functionality)
[ ] This change requires a documentation update
[ ] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[ ] Methods and classes used in PR scenarios are meaningful
[ ] Commits are well encapsulated and follow the best practices

mocenas commented 1 month ago

You probably also need to add quarkus.infinispan-client.sasl-mechanism=DIGEST-SHA-512 into nosql-db/infinispan/src/test/resources/infinispan-it.properties. Please double check that, especially when running on fips and with -Dquarkus.native.builder-image=registry-proxy.engineering.redhat.com/rh-osbs/quarkus-mandrel-for-jdk-21-rhel8:23.1 option

I checked that on FIPS + this image and adding quarkus.infinispan-client.sasl-mechanism=DIGEST-SHA-512 is not necessary - to be more precise, tests pass on FIPS system even without this.

michalvavrik commented 1 month ago

I checked that on FIPS + this image and adding quarkus.infinispan-client.sasl-mechanism=DIGEST-SHA-512 is not necessary - to be more precise, tests pass on FIPS system even without this.

but it's still something that should be done

mocenas commented 1 month ago

I checked that on FIPS + this image and adding quarkus.infinispan-client.sasl-mechanism=DIGEST-SHA-512 is not necessary - to be more precise, tests pass on FIPS system even without this.

but it's still something that should be done

OK, I've checked it works on FIPS machine and added it to PR.