Bug 1239064

Summary: After instack-virt-setup required to ssh the vm as root instead of stack
Product: Red Hat OpenStack Reporter: Attila Fazekas <afazekas>
Component: instack-undercloudAssignee: James Slagle <jslagle>
Status: CLOSED WONTFIX QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 5.0 (RHEL 7)CC: hbrock, jcoufal, kbasil, mburns, nkinder, rhel-osp-director-maint, tvignaud
Target Milestone: Upstream M3Keywords: Reopened, Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-03 00:25:20 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 Attila Fazekas 2015-07-03 12:07:23 UTC 
Description of problem:
The command creates the image with stack user created, but the ssh keys just added to the root user.

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

How reproducible:
always


Actual results:

....
instack vm IP address is 192.168.122.67
You can connect by running:
ssh root.122.67
And then su to the stack user:
su - stack
$
# The stack user does not have my public key in the authorized_keys.

Expected results:
....
instack vm IP address is 192.168.122.67
You can connect by running:
ssh stack.122.67
$

# The stack user has my public keys in the authorized_keys.

Additional info:
It not just better practice, it also simplifies the installation.
Comment 3 Attila Fazekas 2015-07-07 07:40:16 UTC 
I edited the expected result example.

It is sharp edge, unless you do not have strong technical reason to not follow the usual non-root user for ssh practice, please tell me why before you close this bug.
Comment 9 James Slagle 2017-08-03 00:25:20 UTC 
instack-virt-setup is completely gone in OSP12