Bug 1448372 - container-engine failed to start if GROWPART=true was specified in /etc/sysconfig/docker-storage-setup
Summary: container-engine failed to start if GROWPART=true was specified in /etc/sysco...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Giuseppe Scrivano
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks: 1448384 1448800
TreeView+ depends on / blocked
 
Reported: 2017-05-05 10:04 UTC by Gan Huang
Modified: 2017-08-16 19:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-10 05:23:08 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 Gan Huang 2017-05-05 10:04:18 UTC
Description of problem:
container-engine failed to start if GROWPART=true was specified in /etc/sysconfig/docker-storage-setup

Version-Release number of selected component (if applicable):
openshift-ansible-3.6.53-1.git.0.03f33da.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Configure docker-storage-setup on the nodes to be installed
# cat /etc/sysconfig/docker-storage-setup 
VG=rhel
GROWPART=true

2. Run openshift-ansible BYO playbook by setting "openshift_docker_use_system_container" in inventory hosts file


Actual results:

[root@host-8-175-193 ~]# systemctl status container-engine
● container-engine.service - Docker service
   Loaded: loaded (/etc/systemd/system/container-engine.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Fri 2017-05-05 05:47:49 EDT; 15min ago
  Process: 63749 ExecStop=/bin/runc kill container-engine (code=exited, status=1/FAILURE)
  Process: 63646 ExecStart=/bin/runc run container-engine (code=exited, status=1/FAILURE)
  Process: 63644 ExecStartPre=/bin/bash -c export -p > /run/docker-bash-env (code=exited, status=0/SUCCESS)
 Main PID: 63646 (code=exited, status=1/FAILURE)

May 05 05:47:49 host-8-175-193.host.centralci.eng.rdu2.redhat.com systemd[1]: container-engine.service: control process exited, code=exited status=1
May 05 05:47:49 host-8-175-193.host.centralci.eng.rdu2.redhat.com systemd[1]: Unit container-engine.service entered failed state.
May 05 05:47:49 host-8-175-193.host.centralci.eng.rdu2.redhat.com systemd[1]: container-engine.service failed.
May 05 05:47:49 host-8-175-193.host.centralci.eng.rdu2.redhat.com systemd[1]: container-engine.service holdoff time over, scheduling restart.
May 05 05:47:49 host-8-175-193.host.centralci.eng.rdu2.redhat.com systemd[1]: start request repeated too quickly for container-engine.service
May 05 05:47:49 host-8-175-193.host.centralci.eng.rdu2.redhat.com systemd[1]: Failed to start Docker service.
May 05 05:47:49 host-8-175-193.host.centralci.eng.rdu2.redhat.com systemd[1]: Unit container-engine.service entered failed state.
May 05 05:47:49 host-8-175-193.host.centralci.eng.rdu2.redhat.com systemd[1]: container-engine.service failed.

#journalctl -u container-engine
May 05 04:58:13 host-8-175-193.host.centralci.eng.rdu2.redhat.com runc[6967]: ERROR: GROWPART=true is specified and /usr/bin/growpart executable is not available. Install /usr/bin/growpart and try again.


Expected results:


Additional info:

Comment 1 Steve Milner 2017-05-05 16:43:42 UTC
Giuseppe, thoughts on this one?

Comment 2 Giuseppe Scrivano 2017-05-08 16:30:45 UTC
it looks like growpart is missing in the image?  I've just verified it is present in the image based on CentOS.  Adding Jhon as he is taking care of adding the cloud-utils-growpart package to the RHEL build.


Slightly related, I've explicitly added container-storage-setup to Fedora and CentOS:

https://github.com/projectatomic/atomic-system-containers/pull/64

Comment 3 Steve Milner 2017-05-09 21:32:04 UTC
PR Merged. Note that changes won't take effect until jhonce builds the updated container.

Comment 9 errata-xmlrpc 2017-08-10 05:23:08 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.