Deployment with SSH not possible

[youwebmax]

Select Topic Area

Bug

Body

Until around the 25th of November our deployment pipeline was running successfully, but since the 28th of November it has been failing. When running our deploy job, the pipeline fails with the following error.

/home/runner/work/_temp/c32a745b-7578-4bc3-a871-194febe22d86.sh: line 1: ssh-agent: command not found
/home/runner/work/_temp/c32a745b-7578-4bc3-a871-194febe22d86.sh: line 2: install: command not found

This is the step in the deployment job which fails:

      - name: Setting up SSH...
        run: |
          eval "$(ssh-agent -s)"
          install -m 600 -D /dev/null ~/.ssh/id_rsa
          echo "${{ secrets.PRIVATE_KEY }}" | tr -d '\r' > ~/.ssh/id_rsa
          echo "${{ secrets.KNOWN_HOSTS }}" > ~/.ssh/known_hosts
          ssh-add ~/.ssh/id_rsa

This is the start of the job, we are using ubuntu-latest:

jobs:
  deploy-shared:
    runs-on: ubuntu-latest
    environment: ${{ inputs.environment }}
    permissions:
      contents: read
      actions: read
      checks: write
    steps:
    ...

This is the output of the "Set up job" step. Back in November when the pipeline still worked the runner version was 2.320.0, so this might be an issue with the new runner version 2.321.0.

Current runner version: '2.321.0'
Operating System
  Ubuntu
  22.04.5
  LTS
Runner Image
  Image: ubuntu-22.04
  Version: 20241215.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20241215.1/images/ubuntu/Ubuntu2204-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20241215.1
Runner Image Provisioner
  2.0.404.1
GITHUB_TOKEN Permissions
  Actions: read
  Checks: write
  Contents: read
  Metadata: read

This is a shared job, so in order to debug this we've integrated the whole job into the project itself to check if it's a problem with the integration, but we've had the same result. We've also tried it in different projects, but the same error keeps appearing. Does anyone have a similar problem or an idea for a solution?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[youwebmax]

We were able to solve this issue. We had a problematic part in the job config not related to SSH at all which triggered this error. By changing this part the SSH error was resolved.