[CI] :x-pack:plugin:sql:qa:jdbc:security:with-ssl:v7.10.1#bwcTest (fips) failure #66095
Comments
|
Pinging @elastic/es-security (Team:Security) |
|
Another FIPS failure: https://gradle-enterprise.elastic.co/s/3pwpovkmlqieg Same keystore format failure. |
|
@jkakavas The FIPS builds are completely busted and have been for some time. Should we mute this, send the notifications elsewhere, etc? It's causing undue noise for test triage. |
|
I am aware @mark-vieira but the triage and fix process we have right now for FIPS 140 related failures doesn't scale and I'm a bottleneck. We can reroute the notifications temporarily to a different address |
|
Indeed all FIPS stuff goes your direction so perhaps we should route the notifications so test triage isn't the main creator of these issues. Is there a mailing list I can send the FIPS build emails to? Or slack channel, someway that test triage isn't overwhelmed by the noise but these don't fall through the cracks? |
TBC ,the mid/long term goal should be that fips related failures/issues/fixes are handled in the same way as any other CI failure, we're just not there yet(again). It's a constant pain/effort, we were having mostly successful builds a few weeks/months back. There is no list that we can use at the moment, can we create a new google group (build-failures-fips) where we can route these for now, until we are ready to merge them back to the build failures group ? I can make the request tomorrow morning and raise the relevant infra PR if you don't get to it by then. |
|
This is rightly failing. What is concerning is that it just started failing recently. I started failing after #65807 which made sure we apply the fips configuration to the correct plugins and it looks like until that time a lot of projects were not running with the fips configuration as the contents of fips.gradle were not applied. ( This also explains the fury of CI failures after December 8 ) I will mute this project as JDBC client only supports keystores and we can't use JKS/PKCS12 keystores in fips mode, but I'm curious about #65807 @mark-vieira , @breskeby . Could you explain why |
JDBC client can only be configured for SSL with keystores, but we can't use JKS/PKCS12 keystores in FIPS 140-2 mode. Resolves: elastic#66095
Not all projects get My intention is to ditch all that nonsense here soon. The matrix of different project plugins i starting to get out of hand. |
JDBC client can only be configured for SSL with keystores, but we can't use JKS/PKCS12 keystores in FIPS 140-2 mode. Resolves: #66095
JDBC client can only be configured for SSL with keystores, but we can't use JKS/PKCS12 keystores in FIPS 140-2 mode. Resolves: elastic#66095
JDBC client can only be configured for SSL with keystores, but we can't use JKS/PKCS12 keystores in FIPS 140-2 mode. Resolves: elastic#66095
JDBC client can only be configured for SSL with keystores, but we can't use JKS/PKCS12 keystores in FIPS 140-2 mode. Resolves: elastic#66095
Build scan: https://gradle-enterprise.elastic.co/s/elzmdxfctoyi6
(ES_RUNTIME_JAVA=zulu11,nodes=general-purpose)
Repro line: (no reproduce line)
Reproduces locally?: No
Applicable branches: master
Failure history:
Seems to be fips related.
Failure excerpt:
QA module can't start node and build fails:
The text was updated successfully, but these errors were encountered: