mariadb can not start from a host reboot

Bug #1538136 reported by Jeffrey Zhang on 2016-01-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Critical
Jeffrey Zhang

Bug Description

the bootstrap mariadb container use the name "mariadb" with the restart policy=never[0]. However that the mariadb service container also use the name "mariadb", which can not update the restart policy[1]. So the mariadb service container can not resume from a host reboot.

[0] https://github.com/openstack/kolla/blob/87355c231a3bdf17fc1e9b1412f44f85dd549632/ansible/roles/mariadb/tasks/bootstrap.yml#L39-L55
[1] https://github.com/openstack/kolla/blob/87355c231a3bdf17fc1e9b1412f44f85dd549632/ansible/roles/mariadb/tasks/start.yml#L2-L13

Changed in kolla:
assignee: nobody → Jeffrey Zhang (jeffrey4l)

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

Changed in kolla:
status: New → In Progress
Sam Yaple (s8m) on 2016-01-26
Changed in kolla:
status: In Progress → Invalid
Jeffrey Zhang (jeffrey4l) wrote :

Hi Sam, this issue is really existent. How can you mark it Invalid?

Steven Dake (sdake) on 2016-01-28
Changed in kolla:
importance: Undecided → Critical
status: Invalid → In Progress
milestone: none → mitaka-3

Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/272521
Reason: see https://review.openstack.org/#/c/273310/

Reviewed: https://review.openstack.org/272160
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=7e2ce014316677af9b83c42745afe9e42f0c8709
Submitter: Jenkins
Branch: master

commit 7e2ce014316677af9b83c42745afe9e42f0c8709
Author: SamYaple <email address hidden>
Date: Mon Jan 25 16:04:26 2016 +0000

    Cleanup mariadb and make compatiable with mesos

    There is no reason to have a hostname-unique pidfile in the container
    as we currently have. This posed problems with kolla-mesos reusing
    the same script. Since there is no reason for this pidfile to be
    configurable in path _at_ _all_, we hardcode the path.

    Additionally, we adjust the file perm change to only update the perms
    on the folder if it is not already properly set.

    This also incorperates a kolla-ansible file in the bootstrap process
    which follows our other container techniques of using the idempotent
    creation of a volume in the bootstrap process (see nova)

    TrivialFix
    Related-Bug: #1538136
    Change-Id: I2380529fc7146a9603145cdc31e649cb8841f7dd

Changed in kolla:
status: In Progress → Fix Released

Reviewed: https://review.openstack.org/273310
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=6d8959a962c038269653b00ba7ddb491c597e49a
Submitter: Jenkins
Branch: master

commit 6d8959a962c038269653b00ba7ddb491c597e49a
Author: SamYaple <email address hidden>
Date: Thu Jan 28 02:04:02 2016 +0000

    Update all bootstraps to use Label

    Add bootstrap label to all bootstrap containers to ensure that when
    the a new container is launched a difference is seen between it and
    the bootstrap container since we cannot rely on ENV variables for
    this. This only affects mariadb at this stage, but it is needed to
    ensure rabbitmq works when we switch to named volumes.

    Change-Id: Ia022af26212d2e5445c06149848831037a508407
    Closes-Bug: #1538136

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

Other bug subscribers