Bug 1617921

Summary: [3.6] Incomplete default configuration for secure-forward
Product: OpenShift Container Platform Reporter: Birol Bilgin <bbilgin>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED WONTFIX QA Contact: Anping Li <anli>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: anli, aos-bugs, jcantril, kurathod, nhosoi, openshift-bugs-escalate, rmeggins, rromerom, sdodson
Target Milestone: ---   
Target Release: 3.6.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1498398 Environment:
Last Closed: 2019-03-06 21:15:52 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:
Bug Depends On: 1498398    
Bug Blocks:    

Comment 2 Rich Megginson 2018-08-17 17:30:50 UTC
(In reply to Kuunal Rathod from comment #1)
> Please note this is an important Key Account where the customer is using and
> implementing Openshift, and looking on start using Ansible Tower.
> The customer has escalated the case and is asking for resolution.
> We have the risk of losing this customer to the competitors.

I don't understand the urgency - the workaround is simple - just edit the secure forward configuration in the configmap?