Skip to content

[BUG] ProxyCommand missing in ssh gateway arguments. #67934

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jrothrock opened this issue Apr 1, 2025 · 1 comment
Open

[BUG] ProxyCommand missing in ssh gateway arguments. #67934

jrothrock opened this issue Apr 1, 2025 · 1 comment
Labels
Bug broken, incorrect, or confusing behavior needs-triage

Comments

@jrothrock
Copy link

Description
ssh: Could not resolve hostname ssh: Temporary failure in name resolution

It appears that the -oProxyCommand argument was accidentally omitted in the following commit: 7314eb5

Prior to this:

[salt.utils.cloud :2444][DEBUG   ][32115] SSH command: 'ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oControlPath=none -oPasswordAuthentication=no -oChallengeResponseAuthentication=no -oPubkeyAuthentication=yes -oIdentitiesOnly=yes -oKbdInteractiveAuthentication=no -i /etc/salt/saltcloud-us-west-1.key.pem -oConnectTimeout=60 -oProxyCommand="ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oControlPath=none -i /etc/salt/saltcloud-us-west-1.key.pem [email protected] -p 22 nc -q0 %h %p" -p 22 [email protected] date'
[salt.utils.vt.Terminal.PID-32191.STDERR:734 ][DEBUG   ][32115] Warning: Permanently added '[xx.xx.xx.xx]:22' (ED25519) to the list of known hosts.

Following:

[salt.utils.cloud :1182][DEBUG   ][18702] Attempting to authenticate as ubuntu (try 1 of 15)
[salt.utils.cloud :208 ][INFO    ][18702] Using SSH gateway [email protected]:22 nc -q0 %h %p
[salt.utils.cloud :2461][DEBUG   ][18702] SSH command: 'ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oControlPath=none -oPasswordAuthentication=no -oChallengeResponseAuthentication=no -oPubkeyAuthentication=yes -oIdentitiesOnly=yes -oKbdInteractiveAuthentication=no -i /etc/salt/saltcloud-us-west-1.key.pem -oConnectTimeout=60 ssh -oStrictHostKeyChecking=no -oServerAliveInterval=60 -oServerAliveCountMax=3 -oUserKnownHostsFile=/dev/null -oControlPath=none -i /etc/salt/saltcloud-us-west-1.key.pem [email protected] -p 22 nc -q0 %h %p -p 22 [email protected] date'
[salt.utils.vt.Terminal.PID-18751.STDERR:595 ][DEBUG   ][18702] ssh: Could not resolve hostname ssh: Temporary failure in name resolution

Versions Report

salt --versions-report (Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
Salt Version:
          Salt: 3006.10

Python Version:
        Python: 3.10.16 (main, Mar  6 2025, 02:23:15) [GCC 11.2.0]

Dependency Versions:
          cffi: 1.17.1
      cherrypy: unknown
  cryptography: 42.0.5
      dateutil: 2.8.1
     docker-py: Not Installed
         gitdb: Not Installed
     gitpython: Not Installed
        Jinja2: 3.1.6
       libgit2: 1.9.0
  looseversion: 1.0.2
      M2Crypto: Not Installed
          Mako: Not Installed
       msgpack: 1.0.2
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     packaging: 22.0
     pycparser: 2.21
      pycrypto: Not Installed
  pycryptodome: 3.19.1
        pygit2: 1.17.0
  python-gnupg: 0.4.8
        PyYAML: 6.0.1
         PyZMQ: 23.2.0
        relenv: 0.18.1
         smmap: Not Installed
       timelib: 0.2.4
       Tornado: 4.5.3
           ZMQ: 4.3.4
@jrothrock jrothrock added Bug broken, incorrect, or confusing behavior needs-triage labels Apr 1, 2025
Copy link

welcome bot commented Apr 1, 2025

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at [email protected]. We’re glad you’ve joined our community and look forward to doing awesome things with you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior needs-triage
Projects
None yet
Development

No branches or pull requests

1 participant