Bug 1495486 - etcd-3.1 did not upgrade to etcd-3.2 during etcd upgrade
Summary: etcd-3.1 did not upgrade to etcd-3.2 during etcd upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 3.7.z
Assignee: Scott Dodson
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-26 07:37 UTC by liujia
Modified: 2018-04-05 09:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
During the control plane upgrade etcd is now upgraded to etcd 3.2.x.
Clone Of:
Environment:
Last Closed: 2018-04-05 09:28:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 0 None None None 2018-04-05 09:29:03 UTC

Description liujia 2017-09-26 07:37:32 UTC
Description of problem:
Run upgrade_etcd.yml to upgrade etcd, but etcd did not upgrade from 3.1.9 to 3.2.7.
# yum search etcd --showdup
...
============================================================================= N/S matched: etcd =============================================================================
etcd-0.4.6-0.12.el7.x86_64 : A highly-available key value store for shared configuration
etcd-0.4.6-0.13.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.0.9-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.0.11-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.0.13-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.1.1-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.2.2-5.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.2.5-1.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.2.5-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.3.7-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-2.3.7-4.el7.x86_64 : A highly-available key value store for shared configuration
etcd-3.0.15-1.el7.x86_64 : A highly-available key value store for shared configuration
etcd-3.1.0-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-3.1.3-1.el7.x86_64 : A highly-available key value store for shared configuration
etcd-3.1.7-1.el7.x86_64 : A highly-available key value store for shared configuration
etcd-3.1.9-1.el7.x86_64 : A highly-available key value store for shared configuration
etcd-3.1.9-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-3.1.9-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd-3.2.7-1.el7.x86_64 : A highly-available key value store for shared configuration
etcd3-3.0.3-1.el7.x86_64 : A highly-available key value store for shared configuration
etcd3-3.0.14-2.el7.x86_64 : A highly-available key value store for shared configuration
etcd3-3.0.14-2.el7.x86_64 : A highly-available key value store for shared configuration
...

Version-Release number of the following components:
atomic-openshift-utils-3.7.0-0.127.0.git.0.b9941e4.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Install ocp3.6 with etcd version is 3.1.9.
2. Do etcd upgrade before upgrade ocp
# ansible-playbook -i /tmp/rpmha playbooks/byo/openshift-cluster/upgrades/upgrade_etcd.yml
3.

Actual results:
Etcd was not upgraded from 3.1 to 3.2

Expected results:
Etcd should be upgraded to 3.2

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 2 Scott Dodson 2018-01-24 16:14:53 UTC
This is fixed in 3.9 builds and latest 3.7 builds too.

Comment 4 liujia 2018-01-25 06:16:13 UTC
Hit a new issue 1538446 blocked this bug's verify.

Comment 5 liujia 2018-03-05 04:51:09 UTC
openshift-ansible-3.7.36-1.git.0.0f4a93c.el7.noarch

etcd was updated from 3.1.9 to 3.2.11.

Comment 9 errata-xmlrpc 2018-04-05 09:28:25 UTC
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:0636


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