Bug 1561935

Summary: SSH access to the amphoras should be possible after deployment
Product: Red Hat OpenStack Reporter: Alexander Stafeyev <astafeye>
Component: openstack-tripleo-commonAssignee: Carlos Goncalves <cgoncalves>
Status: CLOSED ERRATA QA Contact: Alexander Stafeyev <astafeye>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: amuller, bcafarel, cgoncalves, mburns, nyechiel, slinaber
Target Milestone: rcKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-common-8.6.1-11.el7ost openstack-tripleo-heat-templates-8.0.2-19.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:49:05 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:
Bug Depends On: 1576425    
Bug Blocks: 1433523    

Description Alexander Stafeyev 2018-03-29 08:45:42 UTC
This is a semi-tracker bug. 

At this moment our deployment are not passing keys into the amphora for ssh access. 

We do need those there for debugging and SOS reports.

Comment 2 Nir Magnezi 2018-04-11 13:41:27 UTC
For this bug we would need TripleO to:
1. Undercloud: Generate SSH keypair.
2. Overcloud: Upload to the overcloud Nova
3. Configure octavia.conf https://github.com/openstack/octavia/blob/ec2ecdc2b170f2949c8762bf93166ba93fe53f46/etc/octavia.conf#L205

We would also need to document the private SSH key path in the Undercloud

Comment 3 Carlos Goncalves 2018-04-11 16:37:43 UTC
Reassigning to myself. It will need to be addressed in tripleo-common.

Comment 11 Carlos Goncalves 2018-05-14 07:50:32 UTC
*** Bug 1576425 has been marked as a duplicate of this bug. ***

Comment 15 errata-xmlrpc 2018-06-27 13:49:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.