[CI] HdfsRepositoryAnalysisRestIT class failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic-platform-support #4063 / amazonlinux-2_platform-support-aws
• elasticsearch-periodic-platform-support #4019 / amazonlinux-2_platform-support-aws
• elasticsearch-pull-request #30901 / part-2

Reproduction Line:

undefined

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

undefined

Issue Reasons:

• [main] 3 failures in class org.elasticsearch.repositories.blobstore.testkit.analyze.HdfsRepositoryAnalysisRestIT (0.5% fail rate in 636 executions)
• [main] 2 failures in step amazonlinux-2_platform-support-aws (13.3% fail rate in 15 executions)
• [main] 2 failures in pipeline elasticsearch-periodic-platform-support (12.5% fail rate in 16 executions)

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

[elasticsearchmachine]

This has been muted on branch main

Mute Reasons:

• [main] 2 failures in class org.elasticsearch.repositories.blobstore.testkit.analyze.HdfsRepositoryAnalysisRestIT (0.8% fail rate in 241 executions)

Build Scans:

• elasticsearch-periodic-platform-support #4019 / amazonlinux-2_platform-support-aws
• elasticsearch-pull-request #30901 / part-2

[elasticsearchmachine]

Pinging @elastic/es-distributed (Team:Distributed)

[elasticsearchmachine]

Pinging @elastic/es-distributed (Team:Distributed)

[ywangd]

Relabelling this to low-risk based on the potential usage of the relevant function.

[ywangd]

The failure of the periodical job is

java.io.IOException: java.lang.RuntimeException: Could not resolve Kerberos principal name: java.net.UnknownHostException: i-0a8fbb3cbbdabb028.us-west-2.compute.internal: i-0a8fbb3cbbdabb028.us-west-2.compute.internal: Name or service not known
	at fixture.hdfs3.org.apache.hadoop.http.HttpServer2.<init>(HttpServer2.java:682)
	at fixture.hdfs3.org.apache.hadoop.http.HttpServer2.<init>(HttpServer2.java:129)
	at fixture.hdfs3.org.apache.hadoop.http.HttpServer2$Builder.build(HttpServer2.java:468)
	at fixture.hdfs3.org.apache.hadoop.hdfs.server.namenode.NameNodeHttpServer.start(NameNodeHttpServer.java:152)
	at fixture.hdfs3.org.apache.hadoop.hdfs.server.namenode.NameNode.startHttpServer(NameNode.java:950)
	at fixture.hdfs3.org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:761)
	at fixture.hdfs3.org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:1018)
	at fixture.hdfs3.org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:991)
	at fixture.hdfs3.org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1767)
	at fixture.hdfs3.org.apache.hadoop.hdfs.MiniDFSCluster.createNameNode(MiniDFSCluster.java:1352)
	at fixture.hdfs3.org.apache.hadoop.hdfs.MiniDFSCluster.configureNameService(MiniDFSCluster.java:1121)
	at fixture.hdfs3.org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:994)
	at fixture.hdfs3.org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:926)
	at fixture.hdfs3.org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:554)
	at fixture.hdfs3.org.apache.hadoop.hdfs.MiniDFSCluster$Builder.build(MiniDFSCluster.java:500)
	at org.elasticsearch.test.fixtures.hdfs.HdfsFixture.tryStartingHdfs(HdfsFixture.java:255)
	at org.elasticsearch.test.fixtures.hdfs.HdfsFixture.startMinHdfs(HdfsFixture.java:193)
	at org.elasticsearch.test.fixtures.hdfs.HdfsFixture.before(HdfsFixture.java:85)

Note the UnknownHostException exception. It seems transient to me.

[ywangd]

The other CI failure is on a PR and the error is

Caused by: java.lang.RuntimeException: Unable to locate plugin 'test-features'. Ensure you've added the following to the build script for project ':x-pack:plugin:snapshot-repo-test-kit:qa:hdfs':

which suggests local invalid configuration.

I raised #112906 to unmute the test.