Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1546873

Summary: The upgrade_control_plane.yml playbook leaves etcd leader reporting older version (3.0.15)
Product: OpenShift Container Platform Reporter: Greg Rodriguez II <grodrigu>
Component: Cluster Version OperatorAssignee: Scott Dodson <sdodson>
Status: CLOSED DUPLICATE QA Contact: liujia <jiajliu>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.0CC: aos-bugs, dwatson, jokerman, mmccomas, wmeng
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-20 02:54:42 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 Flags
Ansible log none

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. ***