Fix TestEventLogFile, TestContainerCMDEventToStderr and TestEventLogOutputConfiguredViaFleet

[belimawr]

What does this PR do?

Fix TestEventLogFile, TestContainerCMDEventToStderr and TestEventLogOutputConfiguredViaFleet by updating the string that needs to be searched in the logs.

Why is it important?

It fixes some test that were breaking CI

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

There is no disruptive user impact because this PR is fixing a broken test

How to test this PR locally

Package the Elastic-Agent from this PR:

DEV=true SNAPSHOT=true EXTERNAL=true PACKAGES="deb,rpm,tar.gz" PLATFORMS=linux/amd64 mage -v package

Then run one of the integration test that were failing: TestEventLogFile, TestContainerCMDEventToStderr or TestEventLogOutputConfiguredViaFleet

SNAPSHOT=true TEST_PLATFORMS="linux/amd64" mage -v integration:single  TestEventLogFile

Related issues

• Closes [Flaky Test]: TestEventLogFile – did not find the expected log entry ... in the events log file #5337

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[mergify]

This pull request does not have a backport label. Could you fix it @belimawr? 🙏
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.

[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

[ycombinator]

Looks like TestEventLogOutputConfiguredViaFleet failed in CI:

=== RUN   TestEventLogOutputConfiguredViaFleet
    container_cmd_test.go:75: Creating enrollment API key...
    fetcher.go:93: Using existing artifact elastic-agent-8.16.0-SNAPSHOT-linux-x86_64.tar.gz
    fixture.go:282: Extracting artifact elastic-agent-8.16.0-SNAPSHOT-linux-x86_64.tar.gz to /tmp/TestEventLogOutputConfiguredViaFleet2549331463/001
    fixture.go:300: Completed extraction of artifact elastic-agent-8.16.0-SNAPSHOT-linux-x86_64.tar.gz to /tmp/TestEventLogOutputConfiguredViaFleet2549331463/001
    fixture.go:900: Components were not modified from the fetched artifact
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    event_logging_test.go:316: 
        	Error Trace:	/home/ubuntu/agent/testing/integration/event_logging_test.go:316
        	            				/home/ubuntu/agent/testing/integration/event_logging_test.go:231
        	Error:      	Condition never satisfied
        	Test:       	TestEventLogOutputConfiguredViaFleet
        	Messages:   	could not find event log file
    container_cmd_test.go:98: >> cleaning up: killing the Elastic-Agent process
--- FAIL: TestEventLogOutputConfiguredViaFleet (88.16s)

[belimawr]

Looks like TestEventLogOutputConfiguredViaFleet failed in CI:

=== RUN   TestEventLogOutputConfiguredViaFleet
    container_cmd_test.go:75: Creating enrollment API key...
    fetcher.go:93: Using existing artifact elastic-agent-8.16.0-SNAPSHOT-linux-x86_64.tar.gz
    fixture.go:282: Extracting artifact elastic-agent-8.16.0-SNAPSHOT-linux-x86_64.tar.gz to /tmp/TestEventLogOutputConfiguredViaFleet2549331463/001
    fixture.go:300: Completed extraction of artifact elastic-agent-8.16.0-SNAPSHOT-linux-x86_64.tar.gz to /tmp/TestEventLogOutputConfiguredViaFleet2549331463/001
    fixture.go:900: Components were not modified from the fetched artifact
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    fixture.go:657: >> running binary with: [/tmp/TestEventLogOutputConfiguredViaFleet2549331463/001/elastic-agent-8.16.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
    event_logging_test.go:316: 
        	Error Trace:	/home/ubuntu/agent/testing/integration/event_logging_test.go:316
        	            				/home/ubuntu/agent/testing/integration/event_logging_test.go:231
        	Error:      	Condition never satisfied
        	Test:       	TestEventLogOutputConfiguredViaFleet
        	Messages:   	could not find event log file
    container_cmd_test.go:98: >> cleaning up: killing the Elastic-Agent process
--- FAIL: TestEventLogOutputConfiguredViaFleet (88.16s)

I believe it failed due to the flakiness reported on #5159. I'm working on reproducing this case.

[ycombinator]

Going to backport this PR to unblock some of the backport PRs where these tests are failing.