Bug 1596007

Summary: Fail to redeploy etcd cert on standalone etcd host
Product: OpenShift Container Platform Reporter: Gaoyun Pei <gpei>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED DEFERRED QA Contact: Gaoyun Pei <gpei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.10.0CC: aos-bugs, jokerman, mmccomas, rteague
Target Milestone: ---   
Target Release: 3.10.z   
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-11-19 21:00:10 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:

Description Gaoyun Pei 2018-06-28 03:26:54 UTC
Description of problem:
When trying to redeploy etcd certificates on standalone etcd host, playbook failed at restarting etcd service. It doesn't have master restart script configured for it's installed as a rpm etcd.

TASK [etcd : restart etcd] **************************************************************************************************************************************************
fatal: [ec2-35-173-195-157.compute-1.amazonaws.com]: FAILED! => {"changed": false, "cmd": "/usr/local/bin/master-restart etcd", "failed": true, "msg": "[Errno 2] No such file or directory", "rc": 2}


Version-Release number of the following components:
openshift-ansible-3.10.9-1.git.240.1c86105.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.Run etcd cert redeployment playbook against an ocp-3.10 cluster with standalone etcd host.
#ansible-playbook -i host /usr/share/ansible/openshift-ansible/playbooks/openshift-etcd/redeploy-certificates.yml


Actual results:
Ansible inventory file and full log of playbook could be found in attachments


Expected results:

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

Comment 2 Russell Teague 2018-11-19 21:00:10 UTC
There appear to be no active cases related to this bug. As such we're closing this bug in order to focus on bugs that are still tied to active customer cases. Please re-open this bug if you feel it was closed in error or a new active case is attached.