| Summary: | Route-specific Timeouts configuration described in 3.2 doc doesn't work on 3.2 router image | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Miheer Salunke <misalunk> |
| Component: | Networking | Assignee: | Ben Bennett <bbennett> |
| Networking sub component: | router | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | aos-bugs, bbennett, eparis, knakayam |
| Version: | 3.2.0 | Keywords: | Reopened |
| 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: | 2016-10-14 14:45:29 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: | |
|
Description
Miheer Salunke
2016-10-11 15:40:04 UTC
This is a 3.3 feature that the docs were incorrectly merged over into 3.2. Unfortunately, we can not just add this feature to 3.2. It is part of a much larger change that we can not back-port because it breaks compatibility with the config file. I think the best that you can do for now is change the global timeout until 3.3 is available. I'm sorry for the confusion. This has been reverted in the docs. https://github.com/openshift/openshift-docs/pull/3042 Hi, Original bz also set as "3.2.0" below: https://bugzilla.redhat.com/show_bug.cgi?id=1341312 I'm sorry, but we cannot accept multiple human error. Please fix this issue in 3.2. The BZ above (#1341312) was a feature request opened with the Version set to 3.2. This is not in any way an indication of when the feature will be implemented. Typically the 'Version' is set, by the bug creator, to whatever is the most current version at the time they open the request. Engineering implemented and released this feature in 3.3. We are unable to backport this feature to 3.2 as it builds upon other, non backwards compatible, changes to the router template implemented in 3.3. We do greatly apologize that the docs for 3.2 were mistakenly updated. However, at this time the docs are correct. These features have been added to 3.3 and they are not (mistakenly) discussed in the 3.2 docs. If a customer needs this feature they will need to move to 3.3. I am sorry but because of both the size of the work and the fact that it would break 3.2 systems we will be unable to backport this work to 3.2. > However, at this time the docs are correct. I'm sorry, I don't think so. Could you please check the parameters described around "Configuration Parameters" (Table 1. Router Configuration Parameters) in https://docs.openshift.com/enterprise/3.2/architecture/core_concepts/routes.html#available-router-plug-ins ROUTER_SYSLOG_ADDRESS, ROUTER_LOG_LEVEL and so on.... @Ben, @Eric Below information in same documentation is not true, is it? https://docs.openshift.com/enterprise/3.2/architecture/core_concepts/routes.html#available-router-plug-ins """ Configuration Parameters With all the items outlined in this section, you should be able to set environment variables on the deployment config for the router to alter its configuration. Table 1. Router Configuration Parameters ROUTER_SYSLOG_ADDRESS ROUTER_LOG_LEVEL ROUTER_BACKEND_CHECK_INTERVAL ROUTER_DEFAULT_CONNECT_TIMEOUT XROUTER_DEFAULT_CLIENT_TIMEOUT ROUTER_DEFAULT_SERVER_TIMEOUT ROUTER_DEFAULT_TUNNEL_TIMEOUT ROUTER_SLOWLORIS_TIMEOUT """" @Kenjiro: You are right, another doc change was committed to the wrong branch. I've requested that be reverted too. I am now going through all doc commits to 3.2 to make sure that they were correctly applied to the right branch. |