Bug 1617921 - [3.6] Incomplete default configuration for secure-forward
Summary: [3.6] Incomplete default configuration for secure-forward
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.6.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1498398
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-16 07:20 UTC by Birol Bilgin
Modified: 2019-03-06 21:15 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1498398
Environment:
Last Closed: 2019-03-06 21:15:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-ansible pull 5652 0 None None None 2018-08-16 07:20:19 UTC
Github openshift origin-aggregated-logging pull 740 0 None None None 2018-08-16 07:20:19 UTC
Red Hat Product Errata RHSA-2018:2013 0 None None None 2018-08-16 07:20:19 UTC

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?
Note You need to log in before you can comment on or make changes to this bug.