Bug 1509124 - Encounter node service restart failure during openshift CA redeployment
Summary: Encounter node service restart failure during openshift CA redeployment
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.7.0
Assignee: Andrew Butcher
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-03 06:59 UTC by Gaoyun Pei
Modified: 2017-11-28 22:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-28 22:21:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

Description Gaoyun Pei 2017-11-03 06:59:53 UTC
Description of problem:
Run openshift CA certs redeployment playbook against an ha-master ocp-3.7 cluster, it fails at "TASK [restart node]" 

TASK [Wait for master API to come back online] ******************************************************************************************************************************
ok: [ec2-54-242-50-70.compute-1.amazonaws.com] => {"changed": false, "elapsed": 23, "failed": false, "path": null, "port": 443, "search_regex": null, "state": "started"}

TASK [restart node] *********************************************************************************************************************************************************
fatal: [ec2-54-242-50-70.compute-1.amazonaws.com]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to restart service atomic-openshift-node: Job for atomic-openshift-node.service failed because the control process exited with error code. See \"systemctl status atomic-openshift-node.service\" and \"journalctl -xe\" for details.\n"}
	to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/redeploy-openshift-ca.retry


Version-Release number of the following components:
openshift-ansible-3.7.0-0.190.0.git.0.129e91a.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1.Run redeploy-openshift-ca.yml to update the openshift CA cert files
ansible-playbook -i host /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/redeploy-openshift-ca.yml -v


Actual results:

Expected results:

Additional info:
Ansible inventory file, ansible output of running redeploy-openshift-ca.yml, the logs of atomic-openshift-master-api and atomic-openshift-node on the first master attached.

Comment 7 Gaoyun Pei 2017-11-08 04:33:36 UTC
Verify this bug with openshift-ansible-3.7.0-0.197.0.git.0.f40c09c.el7.noarch.rpm

OpenShift CA certs could be updated successfully by playbooks/byo/openshift-cluster/redeploy-openshift-ca.yml. No error during the redeployment.

Comment 10 errata-xmlrpc 2017-11-28 22:21:23 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/RHSA-2017:3188


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