Bug 1572763
| Summary: | Need to validate etcd server certs have proper SAN prior to upgrading to etcd-3.2.15-2.el7 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
| Component: | Cluster Version Operator | Assignee: | Vadim Rutkovsky <vrutkovs> |
| Status: | CLOSED ERRATA | QA Contact: | Gaoyun Pei <gpei> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.7.1 | CC: | aos-bugs, bleanhar, dma, ghuang, gpei, jokerman, mbarnes, mifiedle, mmccomas, sreber, vlaad, vrutkovs |
| Target Milestone: | --- | ||
| Target Release: | 3.7.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
etcd 3.2.15 is compiled with go 1.9, which tightens the certificate security
Consequence:
Certificates, created without SAN entry, are now treated as invalid in etcd 3.2.15
Fix:
Certificates are re-generated on 3.6 -> 3.7 upgrade so that these would be compatible with new etcd
Result:
openshift-ansible generates valid certificates for etcd 3.2.15
|
Story Points: | --- |
| Clone Of: | 1565762 | Environment: | |
| Last Closed: | 2018-05-07 20:20:14 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: | 1565762 | ||
| Bug Blocks: | |||
|
Comment 1
Scott Dodson
2018-04-30 12:39:07 UTC
Verify this bug with openshift-ansible-3.7.44-1.git.9.684c638.el7.noarch Etcd server.crt issue was fixed during upgrade to 3.7. Detailed steps could be found in https://bugzilla.redhat.com/show_bug.cgi?id=1565762#c7. 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-2018:1335 |