-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unable to add host due to networking or authentification error #7437
Comments
@MilanHofmann Regarding adding host via ssh key, please refer to cloudstack documentation: https://docs.cloudstack.apache.org/en/latest/installguide/configuration.html#adding-a-host
|
@weizhouapache yes I did that. |
@weizhouapache Can you give me a hint, why this is suddenly not possible anymore and how I maybe give the right permsissions for an automatic setup? |
@MilanHofmann |
@weizhouapache 4.18 |
@MilanHofmann
|
I have removed the files and even reinstalled the operating system on the host. |
@MilanHofmann |
@weizhouapache |
If anyone stumbles across this unable to find the CloudStack ssh public key, I finally found on Ubuntu 20.04 -- it was in |
yes, the location is different on OSes. on centos, the location is
we need to update the doc |
@MilanHofmann |
@weizhouapache |
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
advanced networking with KVM
OS / ENVIRONMENT
Ubuntu focal fossa
SUMMARY
I am not able to add a host to a zone.
In the ui a message pops up "Unable to reach the management server or a browser extension may be blocking the network request. in the ui".
the mangement server cloudstack service status says "trying to add new host ip-address Failed to authenticate with ssh key, retrying with password." - Although i selected password as auth method.
When adding the ssh key, and selecting the option for system ssh key I get "Could not add host at [http://ip-address/] with zone [1], pod [1] and cluster [1] due to: [Authentication error with ssh private key]."
BUT:
ssh root@ip-address from the management server works just fine, as well as the usual password auth.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: