## 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.
*** This bug has been marked as a duplicate of bug 1331858 ***
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.