Bug 1444748 - Fail to container install OCP3.6 due to etcd_container can not start based an unexisted file /etc/sysconfig/etcd
Summary: Fail to container install OCP3.6 due to etcd_container can not start based an...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Jan Chaloupka
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-24 07:54 UTC by liujia
Modified: 2017-08-10 05:21 UTC (History)
5 users (show)

Fixed In Version: openshift-ansible-3.6.38-1.git.0.ff78e5c.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-10 05:21:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 09:02:50 UTC

Description liujia 2017-04-24 07:54:03 UTC
Description of problem:
Trigger container install ocp3.6, installation failed on task [openshift_master : Verify API Server] due to etcd_container can not be started based an unexisted file /etc/sysconfig/etcd.

#vi /etc/systemd/system/etcd_container.service
ExecStart=/usr/bin/docker run --name etcd_container --rm -v /var/lib/etcd:/var/lib/etcd:z -v /etc/etcd:/etc/etcd:ro --env-file=/etc/etcd/etcd.conf --env-file=/etc/sysconfig/etcd --net=host --entrypoint=/usr/bin/etcd registry.access.redhat.com/rhel7/etcd


# journalctl -u etcd_container
Apr 24 03:12:59 openshift-109.x.x.x systemd[1]: Starting The Etcd Server container...
Apr 24 03:12:59 openshift-109.x.x.x etcd_container[1491]: Error response from daemon: No such container: etcd_container
Apr 24 03:12:59 openshift-109.x.x.x systemd[1]: Started The Etcd Server container.
Apr 24 03:12:59 openshift-109.x.x.x etcd_container[1497]: /usr/bin/docker-current: open /etc/sysconfig/etcd: no such file or directory.
Apr 24 03:12:59 openshift-109.x.x.x etcd_container[1497]: See '/usr/bin/docker-current run --help'.
Apr 24 03:12:59 openshift-109.x.x.x systemd[1]: etcd_container.service: main process exited, code=exited, status=125/n/a
Apr 24 03:12:59 openshift-109.x.x.x etcd_container[1503]: Error response from daemon: No such container: etcd_container
Apr 24 03:12:59 openshift-109.x.x.x systemd[1]: etcd_container.service: control process exited, code=exited status=1
Apr 24 03:12:59 openshift-109.x.x.x systemd[1]: Unit etcd_container.service entered failed state.
Apr 24 03:12:59 openshift-109.x.x.x systemd[1]: etcd_container.service failed.



Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.6.35-1.git.0.e751716.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Trigger container install(all in one) with external etcd.
2.
3.

Actual results:
Fail to container install OCP3.6.

Expected results:
Install ocp successfully.

Additional info:
QE suggest to add etcd service check during installation to ensure etcd service is started before install and start master/node service.

Comment 1 Jan Chaloupka 2017-05-12 14:11:44 UTC
The fix [1] is merged and built in openshift-ansible-3.6.38-1.git.0.ff78e5c.el7 [2]

[1] https://github.com/openshift/openshift-ansible/pull/3955
[2] https://brew.engineering.redhat.com/brew/buildinfo?buildID=553727

Comment 3 liujia 2017-05-15 09:21:34 UTC
Version:
atomic-openshift-utils-3.6.65.4-1.git.0.6de1866.el7.noarch

Steps:
1. Trigger container install(all in one) with external etcd.

Result:
Install successfully.

Comment 5 errata-xmlrpc 2017-08-10 05:21:25 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/RHEA-2017:1716


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