Bug 1383695 - Make https://docs.openshift.com/container-platform/3.3/admin_guide/router.html#viewing-logs work in 3.2
Summary: Make https://docs.openshift.com/container-platform/3.3/admin_guide/router.htm...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-11 13:07 UTC by Miheer Salunke
Modified: 2019-12-16 07:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-12 14:59:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Miheer Salunke 2016-10-11 13:07:04 UTC
Description of problem:

Make https://docs.openshift.com/container-platform/3.3/admin_guide/router.html#viewing-logs work in 3.2

So how can one achieve this in 3.2 ?

The PR seems to https://github.com/openshift/origin/pull/8332
So it seems we will need to build a router image to have this feature incorprated to work with 3.2
Will this be supported ?If yes then can you please give us the steps to build this router image with the fix in the above mentioned PR

Version-Release number of selected component (if applicable):
3.2

How reproducible:
Always

Steps to Reproduce:
1.In 3.2 follow  https://docs.openshift.com/container-platform/3.3/admin_guide/router.html#viewing-logs
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 zhaozhanqi 2016-10-12 02:32:42 UTC
hi, Miheer

   you can try replace the haproxy-config.template file of router for details :https://docs.openshift.com/container-platform/3.3/install_config/router/customized_haproxy_router.html#using-configmap-replace-template

Comment 3 Ben Bennett 2016-10-12 14:46:15 UTC
We don't intend to back-port that change.  But you could follow the guide zhaozhanqi linked to.  However, changes to the router template aren't officially supported, so if you encounter a bug you may need to restore the original template.


Note You need to log in before you can comment on or make changes to this bug.