Bug 1059136
| Summary: | kie-config-cli fails if host where system repository git is running is not in known_hosts | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||
| Component: | Business Central | Assignee: | Maciej Swiderski <mswiders> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Radovan Synek <rsynek> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0.0 | CC: | kverlaen | ||||
| Target Milestone: | ER1 | ||||||
| Target Release: | 6.0.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-06 20:03:26 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: | |||||||
| Attachments: |
|
||||||
fixed, now kie-config-cli will ask when server is not known host before connecting there was single, cumulative commit for recent issues with kie-config-cli as separate commits would make it more difficult due to extensive changes kie-wb-distributions master: https://github.com/droolsjbpm/kie-wb-distributions/commit/b383c49db9f0b4b341fb9bbbe964f2300885602f 6.0.x: https://github.com/droolsjbpm/kie-wb-distributions/commit/653cbff5720f5138c91eb47c9d6aef7f1ab1a086 Verified with BPMS-6.0.1.ER1 |
Created attachment 856964 [details] error message For the first time kie-config-cli tries to connect to a host via ssh protocol, user is asked if he wants to continue connecting to that host: The authenticity of host 'localhost' can't be established. DSA key fingerprint is b8:f5:87:5d:63:98:78:69:f0:3e:74:ab:d7:27:14:42. Are you sure you want to continue connecting? normally, user would type "yes" and could continue with his work, but kie-config-cli doesn't ask for yes/no, it instead throws an exception (see an attachment) and exits.