fix: enable agent status check

[kuisathaverat]

revert #1017

closes #1022

[mergify]

This pull request does not have a backport label. Could you fix it @kuisathaverat? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[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-12-30T11:43:39.081+0000

• Duration: 93 min 47 sec

Test stats 🧪

Test	Results
Failed	9
Passed	23
Skipped	0
Total	32

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_10_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_10_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 / fleet_ubuntu_22_04_amd64_fleet_mode / Deploying the agent including command line --tag for tags – Fleet Mode

Expand to view the error details

 Step the elastic agent index contains the tags 

• no stacktrace

Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from latest – Upgrade Agent

Expand to view the error details

 Step certs are installed 

• no stacktrace

Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 8.3.0 – Upgrade Agent

Expand to view the error details

 Step agent is in "latest" version: version mismatch required '8.7.0-SNAPSHOT' retrieved '8.3.0' 

• no stacktrace

Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 8.2.0 – Upgrade Agent

Expand to view the error details

 Step agent is in "latest" version: version mismatch required '8.7.0-SNAPSHOT' retrieved '8.2.0' 

• no stacktrace

Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 8.1.3 – Upgrade Agent

Expand to view the error details

 Step agent is in "latest" version: version mismatch required '8.7.0-SNAPSHOT' retrieved '8.1.3' 

• no stacktrace

Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 8.1.0 – Upgrade Agent

Expand to view the error details

 Step agent is in "latest" version: version mismatch required '8.7.0-SNAPSHOT' retrieved '8.1.0' 

• no stacktrace

Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 7.17.8 – Upgrade Agent

Expand to view the error details

 Step agent is in "latest" version: version mismatch required '8.7.0-SNAPSHOT' retrieved '7.17.8' 

• no stacktrace

Steps errors

Expand to view the steps failures

Run tests in the node

• Took 33 min 30 sec . View more details here
• Description: make -C .ci run-tests

Run tests in the node

• Took 50 min 25 sec . View more details here
• Description: make -C .ci run-tests

Run tests in the node

• Took 19 min 47 sec . View more details here
• Description: make -C .ci run-tests

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'hudson.AbortException: 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_10_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_10_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_fleet_mode / Deploying the agent including command line --tag for tags – Fleet Mode
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from latest – Upgrade Agent
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 8.3.0 – Upgrade Agent
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 8.2.0 – Upgrade Agent
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 8.1.3 – Upgrade Agent
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 8.1.0 – Upgrade Agent
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_upgrade_agent / Upgrading an installed agent from 7.17.8 – Upgrade Agent

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.