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

failed ssh connect on install advises me to use --key option which doesn't exist #3188

Closed
elmiko opened this issue Feb 25, 2020 · 4 comments
Closed
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@elmiko
Copy link
Contributor

elmiko commented Feb 25, 2020

Version

$ openshift-install version
openshift-install 4.5.0-0.ci-2020-02-25-115851
built from commit eb0a55adf271bd6b148c7c12a2c796cbb7d6d05a
release image registry.svc.ci.openshift.org/ocp/release@sha256:b870b4cc5958eeeca3efeae913d72247ad2a5eba46db8a91be49d866ff53b008

Platform: aws

What happened?

i was performing an install and it failed, in the output from the failed command was this line telling me to use the --key flag to specify my key.

ERROR Attempted to gather debug logs after installation failure: failed to create SSH client, ensure the private key is added to your auth
entication agent (ssh-agent) or specified with the --key parameter: ssh: handshake failed: ssh: unable to authenticate, attempted methods 
[none publickey], no supported methods remain                                                                                             

this option does not appear to be valid.

FATA[0000] Error executing openshift-install: unknown flag: --key 

What you expected to happen?

i expected the installer tool to pick up my private key through the --key flag.

How to reproduce it (as minimally and precisely as possible)?

$ openshift-install create cluster --dir=mycluster --key=mykey

Anything else we need to know?

References

patrickdillon added a commit to patrickdillon/installer that referenced this issue Mar 6, 2020
The gather bootstrap error message specifies to use the --key command to specify a key. When that error message is shown after running create cluster, users may think the --key flag is available in the create cluster command.

Addresses: openshift#3188
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 5, 2020
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 5, 2020
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link
Contributor

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants