Bug 1374508 - etcd version matching and installer configurations
Summary: etcd version matching and installer configurations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.3.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Timothy St. Clair
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-08 21:14 UTC by Timothy St. Clair
Modified: 2017-03-08 18:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-02-16 21:04:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Timothy St. Clair 2016-09-08 21:14:11 UTC
Description of problem:
At the 11th hour of the 1.4 release, upstream had uncovered an issue with the version of etcd that they had shipped with 1.3.6.  This version has seen some panics in production, and could cause potential rollback issues on an etcd3 update.  This is not an issue for etcd in our rhel-extras channels but is an issue for the embedded etcd in ocp.   

Version-Release number of selected component (if applicable):
etcd-v2.3.0-284 embedded in ocp

Upstream issue with details on panic and potential fall-out: 
https://github.com/kubernetes/kubernetes/issues/32253

resolution:
Update embedded version to 2.3.7+

Comment 1 Derek Carr 2016-09-09 17:13:24 UTC
This is targeting 3.3.1 and not 3.3.0, so marking it as UpcomingRelease.

Tim, correct me if I am misunderstanding the issue or desired effect.

Comment 2 Timothy St. Clair 2016-09-09 18:23:22 UTC
per discussion I'm repurposing this issue to ensure the following: 

1. Client library version matches released version (minor)

2. Only allow installer to install w/external etcd. (may need a clone).

Comment 8 Timothy St. Clair 2017-01-04 19:31:54 UTC
No longer an issue for 3.4 

Client version embedded >> then supported release version of etcd.

Comment 9 Troy Dawson 2017-02-16 21:04:02 UTC
This bug was fixed with the latest OCP 3.4.0 that is already released.


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