💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

Mmm, it seems not resolved for this branch, as I can still see the same errors for 8.1

Do you think it could be a real bug on 8.1? 🤔

I will try to reproduce it locally.

UPDATE: checking the logs of Filebeat run inside the Agent Pod I found the following:

{"log.level":"error","@timestamp":"2022-03-15T08:11:08.305Z","log.logger":"publisher_pipeline_output","log.origin":{"file.name":"pipeline/client_worker.go","file.line":150},"message":"Failed to connect to backoff(elasticsearch(http://elasticsearch:9200)): Connection marked as failed because the onConnect callback failed: Elasticsearch is too old. Please upgrade the instance. If you would like to connect to older instances set output.elasticsearch.allow_older_versions to true. ES=8.1.0, Beat=8.2.0.","service.name":"filebeat","ecs.version":"1.6.0"}

It seems that ES version is 8.1 while Beat+Agent is 8.2, wondering how these versions are set on top level. However not sure if this is the problem with the CI failure since locally I only set BEAT_VERSION. @mdelapenya any ideas?

I've verified that the initial variables are properly set to 8.1:

[2022-03-15T06:58:03.217Z] INFO [2022-03-15T06:58:03Z] Initial artifact versions defined BeatVersion=8.1.1-da392dcd-SNAPSHOT BeatVersionBase=8.1.1-da392dcd-SNAPSHOT ElasticAgentVersion=8.1.1-da392dcd-SNAPSHOT KibanaVersion=8.1.1-da392dcd-SNAPSHOT StackVersion=8.1.1-da392dcd-SNAPSHOT

How are you seeing that 8.2 version for Beats/agent?

With export ELASTIC_AGENT_VERSION=8.1.0 and export BEAT_VERSION=8.1.0 locally the suite passes:

5 scenarios (5 passed)
22 steps (22 passed)
6m48.240438565s
testing: warning: no tests to run
PASS
ok  	github.com/elastic/e2e-testing/e2e/_suites/kubernetes-autodiscover	408.655s

It happens that the first time I execute the suite for a specific version it will exceed the deadline cause the image is not present. Maybe we hit something similar here?

I re-triggered the tests on this to check if it was an issue with the download time.

With export ELASTIC_AGENT_VERSION=8.1.0 and export BEAT_VERSION=8.1.0 locally the suite passes:

In this branch, what happens if you do not export the variables? Because we are in the 8.1 branch, it should use the hashed versions (daily snapshots) for 8.1

Seems that we miss jq tool in 8.1?:
8.1:

VS

main:

@mdelapenya Not sure why #2141 did not make it to 8.1 but it seems to be ok now.

@mdelapenya Not sure why #2141 did not make it to 8.1 but it seems to be ok now.

Interesting... It could be possible that 8.1 branch was created in the same time window that we were doing the backports and for that reason it was missed: I see that we intentionally added the backport labels for 7.16, 7.17 and 8.0 in that PR, so it could mean that 8.1 branch was not there yet.

This also explains why it consistently fails for 8.1.

OTOH, why installing jq in the pod fixes the issue?

jq is used to filter json responses from ES indexes. if jq is not installed the curl and "write-to-file" at

Checking #2231 too.