Bug 1412829
| Summary: | [Backport] Extended Route Validation Breaks Included Templates | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ram Ranganathan <ramr> |
| Component: | Networking | Assignee: | Ram Ranganathan <ramr> |
| Networking sub component: | router | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aos-bugs, bleanhar, pdwyer |
| Version: | 3.3.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.3.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously the extended validation in the router was turned OFF by default. In addition, if extended validation was enabled - a route with an expired certificate would be marked as an extended validation failure. The router now admits routes with expired certificates. In addition, this backport beefs up the extended validation with changes made in 3.4 and 3.5 and also turns on extended validation by default.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-22 18:10:57 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: | |||
|
Description
Ram Ranganathan
2017-01-12 22:28:40 UTC
Not sure on the procedure for OSE/OCP - moving this bugz to modified as the PR has merged. @zhaozhanqi was this tested? This is for release 3.3.1 - I saw your comments for the 3.2 backport. Thx @ram yes, I had tested this bug on openshift v3.3.1.11 with image haproxy(openshift3/ose-haproxy-router v3.3.1.11 869735d3be98), this bug already fixed. Move this bug to 'verified' Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0289 |