Bug 1718138
Summary: | Public key authentication missing in Single node deployment document | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | bipin <bshetty> |
Component: | doc-Deploying_RHHI | Assignee: | Laura Bailey <lbailey> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | bipin <bshetty> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhhiv-1.6 | CC: | asriram, fdelorey, rhs-bugs, sabose, sankarshan, sasundar |
Target Milestone: | --- | ||
Target Release: | RHHI-V 1.6.z Async Update | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-05 06:17:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1723361 |
Description
bipin
2019-06-07 04:12:12 UTC
I cleared out everything on both the server (10.18.49.38) and my client and I can now do passwordless ssh from my laptop(client) to the server however the deploy of a single node RHHI still fails with the same ssh error?? There is definitely some step missing. Frank (In reply to Frank DeLorey from comment #5) > I cleared out everything on both the server (10.18.49.38) and my client and > I can now do passwordless ssh from my laptop(client) to the server however > the deploy of a single node RHHI still fails with the same ssh error?? There > is definitely some step missing. > > Frank If you're running the deployment via cockpit, the passwordless ssh setup should be from the server running cockpit. For instance if you access the url at https://server1:9090 from your laptop and deploying RHHI-V on server1, the passwordless ssh should be between server1 to itself (server1) @Frank, can you try Sahina's suggestion? I suspect this will be it, and that could be clearer in the docs, but I want to be sure this solves your issue. Moving the bug as verified, the contents listed in the doc looks good |