Bug 1382581

Summary: [RFE] Is there an option to pass an ssh key to new rhevm instance? (appliance upgrade to 4.0)
Product: Red Hat Enterprise Virtualization Manager Reporter: Marcus West <mwest>
Component: ovirt-hosted-engine-setupAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.3CC: gklein, lsurette, mkalinin, mwest, stirabos, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: integration
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-10 10:00:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marcus West 2016-10-07 05:38:08 UTC 
## Description of problem:

I recently upgraded from 3.6 to 4.0 (hosted-engine, rhv-h).  During the first attempt, new rhevm instance started successfully, but root logins were disabled, so I had to access via the console to put my key on there.

The upgrade did not complete successfully so I gave it another go.  The second time, it did not take the root password I gave it, so I had to start in single user mode to reset the password.

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

ovirt-hosted-engine-setup-2.0.2.2-2.el7ev.noarch
rhevm-appliance-20160922.0-1.x86_64.rhevm.ova

## How reproducible:

Always

## Steps to Reproduce:
1. install 3.6 (hosted-engine, rhv-h)
2. upgrade to 4.0

## Actual results:

Installation of new rhevm instance is successful, but there is no way to log in initially without console access.

## Expected results:

Best: prompt to enter an ssh key
Acceptable: allow root logins via ssh

## Additional info:

Both my upgrade attempts failed to finish clean, although I suspect this would still be the case if they worked.  I know it's best practice to use user accounts for access, but is this even possible with the installer?  I have a bad habit of using root for everything, but mostly because I just manage test systems.
Comment 2 Simone Tiraboschi 2016-10-10 10:00:12 UTC 

*** This bug has been marked as a duplicate of bug 1331858 ***
Comment 3 Marina Kalinin 2016-11-07 04:26:09 UTC 
Marcus, I think we should create a kcs here. Can you please?

The bug where it is going to be implemented is targeted to 4.1:
https://bugzilla.redhat.com/show_bug.cgi?id=1331858

And the documentation already mentions that the ssh keys need to be modified after the upgrade, but imo not in a clear way.