Bug 1387391
Summary: | api-server never initializes when configured with storage-backend=etcd3 - logs flooded with client transport error msgs | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> | ||||||||
Component: | Node | Assignee: | Timothy St. Clair <tstclair> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Mike Fiedler <mifiedle> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 3.4.0 | CC: | aos-bugs, bleanhar, ccoleman, dma, jeder, jokerman, mifiedle, mmccomas, tdawson, tstclair, vlaad | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | aos-scalability-34 | ||||||||||
Fixed In Version: | Doc Type: | No Doc Update | |||||||||
Doc Text: |
undefined
|
Story Points: | --- | ||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2017-01-18 12:43:58 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: | |||||||||||
Attachments: |
|
Description
Mike Fiedler
2016-10-20 18:39:13 UTC
Created attachment 1212615 [details]
api server logs
Created attachment 1212616 [details]
etcd3 cluster leader log with --debug=true
Removing storage-backend=etcd3 from master-config.yaml restores cluster functionality. One note. For a successful migration (etcdctl migrate) you might need a patch to etcdctl. See https://bugzilla.redhat.com/show_bug.cgi?id=1386963#c3 Created attachment 1212633 [details]
api server logs at loglevel=8
Client in openshift is v3.1.0-alpha.1, and I'm guessing it's un-vetted for version compat as things have changed. This has been merged into ose and is in OSE v3.4.0.16 or newer. This specific issue is resolved, although additional issues with running in migrated etcd2->etcd3 clusters are still being investigated. 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:0066 |