Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71537

ssh-add is timing out in a Fargate worker

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ssh-agent-plugin
    • None
    • Jenkins 2.401.1

      I have a Jenkins instance which spins up workers in Fargate. However, the following occurs when I try to run sshagent:
      [ssh-agent] Looking for ssh-agent implementation...
      [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)
      SSH_AUTH_SOCK=/tmp/ssh-BX6ulrCb6Ksu/agent.163
      SSH_AGENT_PID=166
      Running ssh-add (command line suppressed)
      ERROR: Timeout after 1 minutes
      [ssh-agent] Started.[Pipeline]

      {[Pipeline] sh[Pipeline] }

      ERROR: Timeout after 1 minutes
      [ssh-agent] Stopped.[Pipeline] // sshagent
      Any idea why it might be timing out? I imagine were it failing to add the provided key, it would not be a time out, rather an explicit error no?

          [JENKINS-71537] ssh-add is timing out in a Fargate worker

          Chad added a comment -

          I have since moved to using EC2 runners but it still happens. I think I'm bumping into the problem described here:

          Unfortunately, this means that if the Jenkins Agent was forced to create the socket in the system temp instead of the Workspace one, processes inside the container are not able to access it.

          So, I tried to solve it by mounting /tmp in container to /tmp in host. However, though the ssh socket files are now reflected in the host's /tmp, the same problem persists.

          Chad added a comment - I have since moved to using EC2 runners but it still happens. I think I'm bumping into the problem described here : Unfortunately, this means that if the Jenkins Agent was forced to create the socket in the system temp instead of the Workspace one, processes inside the container are not able to access it. So, I tried to solve it by mounting /tmp in container to /tmp in host. However, though the ssh socket files are now reflected in the host's /tmp, the same problem persists.

          Chad added a comment -

          This is almost certainly due to JENKINS-71556.

          Chad added a comment - This is almost certainly due to JENKINS-71556 .

            Unassigned Unassigned
            cestioco Chad
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: