Bug 1596007 - Fail to redeploy etcd cert on standalone etcd host
Summary: Fail to redeploy etcd cert on standalone etcd host
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.10.z
Assignee: Scott Dodson
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-28 03:26 UTC by Gaoyun Pei
Modified: 2018-11-19 21:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 21:00:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1585978 0 high CLOSED Redeploy openshift ca playbook failed 2021-02-22 00:41:40 UTC

Internal Links: 1585978

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.


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