mariadb container fails when dumb-init is unavailable

Bug #1821970 reported by Alex Schultz
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Alex Schultz

Bug Description

If dumb-init is not available, the mysql containers fail to start now because it's not installed. We do not have it available downstream because it's a source based install and we should actually not be installing it upstream either.

stderr: container create failed: container_linux.go:336: starting container process caused \"exec: \\\"dumb-init\\\": executable file not found in $PATH\"

This dumb-init usage was added by https://review.openstack.org/#/c/644244/3/docker/mariadb/Dockerfile.j2

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (master)

Fix proposed to branch: master
Review: https://review.openstack.org/648232

Changed in tripleo:
assignee: nobody → Alex Schultz (alex-schultz)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/648232
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=89cbba272daca16d87429db6400848b911dbfe2f
Submitter: Zuul
Branch: master

commit 89cbba272daca16d87429db6400848b911dbfe2f
Author: Alex Schultz <email address hidden>
Date: Wed Mar 27 14:09:53 2019 -0600

    Stop dumb-init usage

    The dumb-init is actually installed by fetching it from github and
    putting it in the base image. We don't actually want that for our usage.
    Additionally a new block that overrode the entrypoint in the mariadb
    container which now causes the mysql container to fail if dumb-init is
    not installed.

    Change-Id: I2228a0da506daf207ea402d3e5a0f156b629862a
    Closes-Bug: #1821970

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
Alex Schultz (alex-schultz) wrote :

We're reverting this as putting dumb-init back in since the mistral container was leaking ssh processes due to the lack of an init

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 10.6.1

This issue was fixed in the openstack/tripleo-common 10.6.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/stein)

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/680133

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/680134

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.opendev.org/680135

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-common (stable/stein)

Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/680133

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-common (stable/queens)

Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/680135

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-common (stable/rocky)

Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/680134

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.