Bug 1397438

Summary:	unable to SCP to LTM when using F5 integration, require additional option in F5 LTM router deployment
Product:	OpenShift Container Platform	Reporter:	Miheer Salunke <misalunk>
Component:	RFE	Assignee:	Rajat Chopra <rchopra>
Status:	CLOSED DEFERRED	QA Contact:	Xiaoli Tian <xtian>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2.1	CC:	aos-bugs, eparis, jokerman, mbarrett, misalunk, mmccomas, sjavurek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-12 13:54:36 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:

Comment 3 Miheer Salunke 2016-11-22 14:22:29 UTC

1. Proposed title of this feature request
=>unable to SCP to LTM when using F5 integration, require additional option in F5 LTM router deployment



3. What is the nature and description of the request?
=> Our LTM environment is using remote user accounts, as a result we're unable to use the user which we've given access to the LTM via TACAS as the account to SCP PEM certificates to because as per :

https://support.f5.com/kb/en-us/solutions/public/13000/400/sol13454.html#remoteclient

it's not possible to do this.

We need to configure the F5 LTM to use a different user account to SCP, than that it uses to interact with the LTM API, please create a patch to allow this, as you can see in 

https://github.com/openshift/origin/blob/master/pkg/router/f5/f5.go

sshUserHost builds up the ssh command using f5.username which is the same username used for the web API.

We'd like the option to specify SCP User seperately.

Comment 9 Eric Rich 2018-03-12 13:54:36 UTC

This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.