Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Align the version of Elasticsearch/Logstash/Kibana (7.16) across all integration tests and documentation #25663

Merged
merged 7 commits into from
May 21, 2022

Conversation

yrodiere
Copy link
Member

Context: #25648 (comment)

In short, we need at least Elasticsearch 7.11 to run on Apple M1, and the heterogeneous configuration made upgrading the Elasticsearch version difficult.

This makes the Elasticsearch container configuration consistent across all integration tests and bumps the Elasticsearch server version used for tests to 7.16 (also Logstash and Kibana, so technically we're upgrading the whole ELK stack).

I didn't change the version of the client, in particular the High Level REST client, which cannot be upgraded beyond 7.10 because 7.11+ is no longer open-source. However, that's no big deal as the High Level REST client is forward-compatible with Elasticsearch (server) 7.16. We will have a problem when we want to upgrade to Elasticsearch 8.x, but that's a problem for another day.

@quarkus-bot

This comment has been minimized.

@yrodiere yrodiere force-pushed the elasticsearch-it-image-consistency branch from c77f8a7 to 79a45eb Compare May 19, 2022 07:29
@quarkus-bot

This comment has been minimized.

yrodiere added 2 commits May 19, 2022 14:10
…ration tests

docker.elastic.co has been down a few times in the past, dockerhub is
more reliable.

They both serve the exact same images (same tags, same hashes),
so the change should be mostly transparent.
1. Because we don't use it (we always connect unauthenticated)
2. Because we'll need to disable it in Elasticsearch 8+ anyway,
   otherwise Elasticsearch uses a self-signed certificate (which we have
   to allow in the client JVM) and mandates HTTP authentication.
@yrodiere yrodiere force-pushed the elasticsearch-it-image-consistency branch from 79a45eb to 4076577 Compare May 19, 2022 12:10
@quarkus-bot
Copy link

quarkus-bot bot commented May 19, 2022

Failing Jobs - Building 4076577

Status Name Step Failures Logs Raw logs
Devtools Tests - JDK 11 Build Failures Logs Raw logs
Devtools Tests - JDK 17 Build Failures Logs Raw logs
Native Tests - HTTP Build Failures Logs Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Devtools Tests - JDK 11 #

- Failing: integration-tests/devtools 

📦 integration-tests/devtools

io.quarkus.platform.catalog.RegistrySnapshotCatalogCompatibilityTest.testRegistrySnapshotPlatformCatalog line 30 - More details - Source on GitHub

java.lang.IllegalStateException: Failed to locate the dev tools config file (.quarkus/config.yaml)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClient.<init>(TestRegistryClient.java:33)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClientFactory.buildRegistryClient(TestRegistryClientFactory.java:32)

⚙️ Devtools Tests - JDK 17 #

- Failing: integration-tests/devtools 

📦 integration-tests/devtools

io.quarkus.platform.catalog.RegistrySnapshotCatalogCompatibilityTest.testRegistrySnapshotPlatformCatalog line 30 - More details - Source on GitHub

java.lang.IllegalStateException: Failed to locate the dev tools config file (.quarkus/config.yaml)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClient.<init>(TestRegistryClient.java:33)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClientFactory.buildRegistryClient(TestRegistryClientFactory.java:32)

⚙️ Native Tests - HTTP #

- Failing: integration-tests/resteasy-reactive-kotlin/standard 

📦 integration-tests/resteasy-reactive-kotlin/standard

io.quarkus.it.resteasy.reactive.kotlin.NativeReactiveGreetingResourceIT.testHello - More details - Source on GitHub

java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource io.quarkus.it.resteasy.reactive.kotlin.KafkaTestResource@3f376582
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.throwBootFailureException(QuarkusIntegrationTestExtension.java:284)
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.beforeEach(QuarkusIntegrationTestExtension.java:76)

@gsmet
Copy link
Member

gsmet commented May 19, 2022

@quarkusio/devtools the RegistrySnapshotCatalogCompatibilityTest.testRegistrySnapshotPlatformCatalog test is failing for several PRs, could one of you have a look or disable it?

@gsmet
Copy link
Member

gsmet commented May 21, 2022

@@ -103,11 +102,12 @@ version: '3.2'

services:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch-oss:{es-version}
image: {elasticsearch-image}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to include this attribute here:
https://github.com/quarkusio/quarkusio.github.io/blob/develop/_guides/attributes.adoc

Let's do it now so that we don't forget about it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here you go: quarkusio/quarkusio.github.io#1438

I don't really know what I'm doing though; I would have expected this file to be generated. Should I remember to keep it in sync every time we upgrade to a new version of Elasticsearch?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah unfortunately it's not generated. It wasn't when I took over the role and I never took the time to think about how to do this properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants