Bug 799333 - After every reboot of the node (2.2.3-1.1) the ssh keys change
Summary: After every reboot of the node (2.2.3-1.1) the ssh keys change
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 805540
TreeView+ depends on / blocked
 
Reported: 2012-03-02 14:08 UTC by Michel van Horssen
Modified: 2016-04-27 02:18 UTC (History)
7 users (show)

Fixed In Version: 2.3.0
Clone Of:
Environment:
Last Closed: 2012-03-26 20:10:54 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Michel van Horssen 2012-03-02 14:08:55 UTC
Description of problem:

After rebooting the node I wanted to login via ssh again and got a key change warning. After removing the key for this host from known_hosts and accepting the new keys I rebooted the node again to see if the keys would change again and they did.

Mentioning this in IRC yossarianuk noticed the same problem

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

2.2.3-1.1

How reproducible:


Steps to Reproduce:
1. ssh in to the node as admin and accept the key (if its the first time)
2. In the tui menu tell the node to reboot
3. ssh in to the node as admin again, you get a key change warning.

Comment 1 Fabian Deutsch 2012-03-19 13:13:26 UTC
It seems as if the ssh host keys weren't persisted because of a missing back slash.

http://gerrit.ovirt.org/#change,2931

Comment 2 Fabian Deutsch 2012-03-21 10:46:49 UTC
The following patch also fixes this bug for the standalone case:

http://gerrit.ovirt.org/#change,2981

(The previous patch was abandoned)


Note You need to log in before you can comment on or make changes to this bug.