Jenkins builds of amlen failing with bad private key

Summary

Jenkins builds of Amlen fail with an error shown below (It looks very much like this issue:

In Upload, BUILD_LABEL is 20250819-0614_eclipsealmalinux9 [Pipeline] sshagent [ssh-agent] Using credentials genie.amlen (ssh://genie.amlen@projects-storage.eclipse.org) Executing sh script inside container jnlp of pod amlen-almalinux9-build-pod-nhsws-1kzx3 Executing command: "ssh-agent" exit SSH_AUTH_SOCK=/tmp/ssh-2BQ1azvszf08/agent.140; export SSH_AUTH_SOCK; SSH_AGENT_PID=141; export SSH_AGENT_PID; echo Agent pid 141; SSH_AUTH_SOCK=/tmp/ssh-2BQ1azvszf08/agent.140 SSH_AGENT_PID=141 Running ssh-add (command line suppressed) Error loading key "/home/jenkins/agent/workspace/AmlenBuilds_levell-rhel10@tmp/private_key_3537691526232537897.key": error in libcrypto

Example jenkins build failures are:

https://ci.eclipse.org/amlen/job/AmlenBuilds/job/levell-rhel10/

Steps to reproduce

Trigger a rebuild of one of the builds at the jenkins link above

What is the current bug behavior?

Build fails to upload artifacts

What is the expected correct behavior?

Build succeeds

Relevant logs and/or screenshots

(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Priority

Urgent
High
Medium
Low

Severity

Blocker
Major
Normal
Low

Impact

We need to get ready for a new release but no timeline has been set