auditbeat/metricbeat/packetbeat - verify required glibc version

[andrewkroh]

What does this PR do?

Check the minimum required glibc on cross-build artifacts. This is a precautionary check to ensure binaries are aligned the current OS support matrix (https://www.elastic.co/support/matrix).

Why is it important?

Prevent unintended support matrix incompatibilities.

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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

cd auditbeat; PLATFORMS="linux/amd64 linux386" mage -v crossBuild

Related Issues

• Relates Packaging build is failing for 8.7 and main #34938 (comment)

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @andrewkroh? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[efd6]

LGTM

For posterity: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.0_release_notes/sect-red_hat_enterprise_linux-7.0_release_notes-compiler_and_tools-glibc

[cmacknz]

Any reason not to also do this in the Filebeat and Metricbeat builds?

[andrewkroh]

Filebeat already has it. I will add it to Metricbeat.

[elasticmachine]

💚 Build Succeeded

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: 2023-03-28T21:09:59.371+0000

• Duration: 88 min 56 sec

Test stats 🧪

Test	Results
Failed	0
Passed	26086
Skipped	1965
Total	28051

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[andrewkroh]

It looks like this has detected a problem with Packetbeat on linux/386. It won't be able to run on Debian 9 (glibc 2.24) (which is listed on the support matrix). There are a bunch of inconsistencies on the support matrix (the test checks that things run on at least centos 7 (glibc 2.17) b/c I think that is our true minimum requirement).

Error: dynamically linked binary "build/golang-crossbuild/packetbeat-linux-386" requires glibc 2.28.0, but maximum allowed glibc is 2.17.0

[andrewkroh]

I resolution I chose for the x-pack/packetbeat failure was to use the debian9 golang-crossbuild image for the linux/386 build. This produces a binary that requires glibc 2.7.0.