Bug 1546873 - The upgrade_control_plane.yml playbook leaves etcd leader reporting older version (3.0.15)
Summary: The upgrade_control_plane.yml playbook leaves etcd leader reporting older ver...
Keywords:
Status: CLOSED DUPLICATE of bug 1507934
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: liujia
URL:
Whiteboard:
: 1546260 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-19 20:53 UTC by Greg Rodriguez II
Modified: 2021-06-10 14:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-20 02:54:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Ansible log (1.72 MB, text/plain)
2018-02-19 20:53 UTC, Greg Rodriguez II 		no flags Details
View All

Description Greg Rodriguez II 2018-02-19 20:53:41 UTC 
Created attachment 1398027 [details]
Ansible log

Description of problem:
Expected etcd leader to report the newer version (3.1.9) correctly, like the 2 other members do.  During upgrade from 3.5.5.31 to 3.6.173.0.5, using ansible-2.2.3.0 & atomic-openshift-utils-3.6.173.0.48.

How reproducible:
Repeatedly, and is always fixed by restarting etcd service on leader node.

Actual results:
Attaching logs

Expected results:
Expected etcd leader to report the newer version (3.1.9) correctly, fixed by restarting etcd service on leader node

Additional info:
Please attach logs from ansible-playbook with the -vvv flag
Comment 1 Scott Dodson 2018-02-20 02:54:42 UTC 
The control plane upgrade failed due to https://bugzilla.redhat.com/show_bug.cgi?id=1507934

That bug is fixed in openshift-ansible-3.6.173.0.65-1 and later

*** This bug has been marked as a duplicate of bug 1507934 ***
Comment 2 Scott Dodson 2018-02-20 14:55:08 UTC 
*** Bug 1546260 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.