Skip to content
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

Add os-conf to deployment for wings workers to add another user #2920

Open
pivotal-saman-alvi opened this issue Dec 8, 2018 · 1 comment

Comments

@pivotal-saman-alvi
Copy link
Contributor

pivotal-saman-alvi commented Dec 8, 2018

What challenge are you facing?

When trying to fix the wings deployment issue, ran into a case where we could not ssh onto the worker successfully, because of issues with the public_key available in creds. It would be useful to have another user we can use in case we are blocked on being able to login with vcap.

What would make this better?

https://github.com/cloudfoundry/os-conf-release/blob/master/jobs/user_add/spec

@pivotal-saman-alvi
Copy link
Contributor Author

$ bosh -e prod -d concourse-wings ssh worker/id --opts=-v

Using deployment 'concourse-wings'

Task 1240341. Done
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/NinjaDoppleganger/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Executing proxy command: exec ssh -tt -W 10.1.0.11:22 -l bosh-ssh 104.198.208.171 -o ServerAliveInterval=30 -o ForwardAgent=no -o ClearAllForwardings=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
debug1: permanently_drop_suid: 501
debug1: identity file /Users/NinjaDoppleganger/.bosh/tmp/ssh-priv-key533479921 type -1
debug1: identity file /Users/NinjaDoppleganger/.bosh/tmp/ssh-priv-key533479921-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
Warning: Permanently added '104.198.208.171' (RSA) to the list of known hosts.
Unauthorized use is strictly prohibited. All access and activity
is subject to logging and monitoring.
Permission denied (publickey).
ssh_exchange_identification: Connection closed by remote host

Running SSH:
  1 error(s) occurred:

* Running command: 'ssh -tt -o ServerAliveInterval=30 -o ForwardAgent=no -o PasswordAuthentication=no -o IdentitiesOnly=yes -o IdentityFile=/Users/NinjaDoppleganger/.bosh/tmp/ssh-priv-key533479921 -o StrictHostKeyChecking=yes -o UserKnownHostsFile=/Users/NinjaDoppleganger/.bosh/tmp/ssh-known-hosts104525980 -o ProxyCommand=ssh -tt -W %!h(MISSING):%!p(MISSING) -l bosh-ssh 104.198.208.171 -o ServerAliveInterval=30 -o ForwardAgent=no -o ClearAllForwardings=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -v 10.1.0.11 -l bosh_255ae724516148b6', stdout: '', stderr: '': exit status 255

Exit code 1

@vito vito added the triage label Jan 9, 2019
@vito vito removed the triage label Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants