-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Comments
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
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
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. |
Version
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.this option does not appear to be valid.
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
The text was updated successfully, but these errors were encountered: