[automation] update elastic stack version for testing 8.1.0-574d4d37

[apmmachine]

What

Bump stack version with the latest one.

Further details

[start_time:Tue, 1 Mar 2022 12:13:39 GMT, release_branch:8.1, prefix:, end_time:Tue, 1 Mar 2022 17:11:51 GMT, manifest_version:2.0.0, version:8.1.0-SNAPSHOT, branch:8.1, build_id:8.1.0-574d4d37, build_duration_seconds:17892]

[elasticmachine]

💔 Tests Failed

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

Expand to view the summary

Build stats

• Start Time: 2022-03-02T05:13:45.813+0000

• Duration: 76 min 5 sec

Test stats 🧪

Test	Results
Failed	5
Passed	267
Skipped	0
Total	272

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-pod": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:container-in-pod" 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:cronjob-container": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-failing-pod": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:redis": context deadline exceeded 

• no stacktrace

Steps errors

Expand to view the steps failures

Shell Script

• Took 44 min 13 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2194-1-d3cac030-cd39-4c70-b82c-4b7a6b8e143e/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "elastic-agent && ~@nightly && ~@skip:amd64" '

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-03-02T06:29:36.761Z] Archiving artifacts script returned exit code 2

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone

🤖 GitHub comments

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

• /test : Re-trigger the build.

[mdelapenya]

@ChrsMark I started to see these 5 errors as consistent in 8.1. Is there anything in your mind for the root cause?