Skip failing k8s capabilities test

[ycombinator]

What does this PR do?

This PR skips the failing TestKubernetesAgentStandalone/drop_ALL_add_CHOWN,_SETPCAP_capabilities_-_rootless_agent integration test while it's being fixed.

Why is it important?

To unblock Agent PRs that are failing CI only due to this test's failure.

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[mergify]

This pull request does not have a backport label. Could you fix it @ycombinator? 🙏
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 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[pkoutsovasilis]

is this PR needed, given that there is this one open? 🙂

[ycombinator]

is this PR needed, given that there is this one open? 🙂

Whichever one goes in first, and would definitely prefer for that to be #5290 instead of this one 🙂.

[blakerouse]

Being that this PR #5290 fixes the actual issue I would prefer to have it merged and have this on closed.

[ycombinator]

Being that this PR #5290 fixes the actual issue I would prefer to have it merged and have this on closed.

Agreed. Will wait to merge this PR and close it unmerged if #5290 gets merged within the next few hours.

[pkoutsovasilis]

Hi @ycombinator 👋 I think in one CI run (here) you got a failure because the chmoding of the parallel k8s tests (3 kind k8s clusters) were overwhelming the underline machine. Thus I have opened this PR against this branch which essentially makes the k8s integration test run in sequence and increase the timeout of waiting for elastic-agent to report healthy to 120 seconds. Please either cherry pick them from there or merge the PR, I have no issue and include them here. After syncing with @blakerouse and @cmacknz we decided that they best way forward is to unblock the CI for everybody by bringing in your PR first. Afterwards we will get some eyes from the Heartbeat team on the other PR, revert the Agentbeat capabilities PR, and if everything checks out we will merge it 🙂

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[pkoutsovasilis]

LGTM! ty @ycombinator

[ycombinator]

Ugh, now TestLongRunningAgentForLeaks/TestHandleLeak is failing :(

[pkoutsovasilis]

This is expected atm right based on this #5279 ?!
In this PR which was previously open, although the title and description is hinting only at k8s tests failures, it was disabling also some tests that I think overlap with what you are seeing here

• https://github.com/elastic/elastic-agent/pull/5271/files#diff-5a2df879e70cf43c9ba330a864d0fbd238f3ae27b38e61d2b94a3405745d1e4aR599
• https://github.com/elastic/elastic-agent/pull/5271/files#diff-5a2df879e70cf43c9ba330a864d0fbd238f3ae27b38e61d2b94a3405745d1e4aR534

Also it increases the timeout here

• https://github.com/elastic/elastic-agent/pull/5271/files#diff-b062b8ddfa1dd29092f30b99e4dcc8f189fc76d6ec5ecee4c08eec38ebcd539cR154

maybe we should bring these changes here?

[ycombinator]

Thanks @pkoutsovasilis. I'm going to force merge this PR then and we'll deal with #5279 in a separate PR. That way we can revert the two PRs independently as we fix the respective tests for real.