Elastic Agent ARM package are failling

[ph]

Reported by @kuisathaverat

We have detected that the ARM package is failing on the CI, and it should be failing on the release process. The ARM package process runs on an ARM machine, the issue here is that mage package will build a binary for elastic-agent ARM64 that is correct, and Filebeat and Metricbeat for AMD64, and here is the issue, we do not have cross-compilers to build Intel binaries on Arm machines and the mage package is trying to use the x86 Docker images on and Arm that is not possible. This blocks the release of the Elastic Agent for ARM because the unified release process uses the same mage package command.

In the meantime, to allow to unlock PRs the ARM package stage is disabled in beats-ci #26240

thinking about this I think that build x86 binaries in the ARM Elastic Agent is not correct, those binaries can not be executed on the host is running the Elastic Agent (ARM) because that meant for a different architecture (x86).

[elasticmachine]

Pinging @elastic/agent (Team:Agent)

[urso]

Beats build tools make use of cross compilation when build packages for multiple platforms. These packages are not used by CI. The tools used to build the packages require an x86 docker environment. The ARM packaging itself should not be disabled, but ARM test machines should not attempt to build packages at all.

This might be a little tricky for Agent, but if possible, we should try to follow that model.

[blakerouse]

Could we change the Jenkins execution for ARM to only build ARM binaries? I think the PLATFORMS env will already do the correct thing here, instead of removing the job completely.

[kuisathaverat]

Jenkins executes PLATFORMS="linux/arm64" PACKAGES=docker mage package on a ARM machine builds a elastic-agent(linux/arm64)+filebeat(linux/amd64)+metricbeat(linux/amd64) the Filebeat and Metricbeat (linux/amd64) can nor run on the same host that the elastic-agent(linux/arm64) because are different architectures. This will fail in the release process because will use the same commands in the same worker type.