Skip to content

[CI] SimpleSecurityNetty4ServerTransportTests testClientChannelUsesSeparateSslConfigurationForRemoteCluster failing #130669

Open
@elasticsearchmachine

Description

@elasticsearchmachine

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:security:test" --tests "org.elasticsearch.xpack.security.transport.netty4.SimpleSecurityNetty4ServerTransportTests.testClientChannelUsesSeparateSslConfigurationForRemoteCluster" -Dtests.seed=54A39CE6B8BD8061 -Dtests.locale=teo-UG -Dtests.timezone=America/Anchorage -Druntime.java=17 -Dtests.fips.enabled=true

Applicable branches:
8.19

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: (a string containing "unable to find valid certification path" or a string containing "Unable to find certificate chain" or a string containing "Unable to construct a valid chain")
     but: was "Unable to build a CertPath: no PKIXBuilderParameters available"

Issue Reasons:

  • [8.19] 7 consecutive failures in step openjdk17_checkpart4_java-fips-matrix
  • [8.19] 7 failures in test testClientChannelUsesSeparateSslConfigurationForRemoteCluster (2.2% fail rate in 324 executions)
  • [8.19] 7 failures in step openjdk17_checkpart4_java-fips-matrix (100.0% fail rate in 7 executions)
  • [8.19] 7 failures in pipeline elasticsearch-periodic (70.0% fail rate in 10 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

Metadata

Metadata

Assignees

No one assigned

    Labels

    :Security/FIPSRunning ES in FIPS 140-2 mode>test-failureTriaged test failures from CITeam:SecurityMeta label for security teamneeds:riskRequires assignment of a risk label (low, medium, blocker)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions