Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1079552

Summary:	SSH Host Key changes every session
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Adam Baxter <abaxter>
Component:	Business Central	Assignee:	Maciej Swiderski <mswiders>
Status:	CLOSED NOTABUG	QA Contact:	Marek Baluch <mbaluch>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.0	CC:	abaxter, kverlaen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-02 19:40:08 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:

Description Adam Baxter 2014-03-21 19:29:52 UTC

Description of problem:
Every time kie-config-cli accesses KIE-WB, the following warning occurs:

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the DSA host key has just been changed.
The fingerprint for the DSA key sent by the remote host is
d3:c4:22:72:42:72:58:9e:8e:bf:f2:49:12:24:ca:a1.
Please contact your system administrator.
Add correct host key in known_hosts to get rid of this message.
Do you want to delete the old key and insert the new key? [yes|no]:

Version-Release number of selected component (if applicable):
6.0.0+

How reproducible:
Consistent

Steps to Reproduce:
1. Connect to online KIE-WB via kie-config-cli

Actual results:
SSH complains that the host key has changed every session

Expected results:
SSH doesn't complain that the host key has changed every session 

Additional info:

Comment 2 Adam Baxter 2014-03-21 19:33:03 UTC

Tested code is 6.0.1-redhat-3

Comment 3 Maciej Swiderski 2014-03-26 13:29:03 UTC

Adam, could you please provide bit more information about this as I can't seem to reproduce it.

Comment 4 Adam Baxter 2014-04-02 19:40:08 UTC

Appears to be a problem with by known_hosts file. Removing the file outright corrected the problem.