MariaDB fails while scaling out
Bug #1840764 reported by
Dincer Celik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Medium
|
Mark Goddard | ||
Stein |
Fix Released
|
Medium
|
Mark Goddard |
Bug Description
Using stable/stein and some handler tasks fails the deployment while trying to scale out control nodes. Seems the tasks are running despite there's no mariadb container there. I'm attaching the log for scaling out from 3 to 7.
Changed in kolla-ansible: | |
importance: | Undecided → Medium |
Changed in kolla-ansible: | |
status: | New → Incomplete |
status: | Incomplete → Fix Committed |
assignee: | nobody → Mark Goddard (mgoddard) |
milestone: | none → 8.0.1 |
Changed in kolla-ansible: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/677453 /git.openstack. org/cgit/ openstack/ kolla-ansible/ commit/ ?id=074d254b089 1f9648de9ef8b98 2a3555e8c1f036
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 074d254b0891f96 48de9ef8b982a35 55e8c1f036
Author: Mark Goddard <email address hidden>
Date: Tue Aug 20 12:39:44 2019 +0100
Don't stop mariadb slaves if they aren't running
Stein only
If mariadb is not running on all of the slave nodes during a deploy,
reconfigure or upgrade, then currently the "remove restart policy from
slave mariadb" handler will fail on nodes where the container does not
exist. A valid use case for this is when scaling out the cluster, but it
could also happen if the slaves are down for some other reason.
This change checks if the mariadb container exists on slaves, and skips
all shutdown related tasks on slaves where it does not.
Change-Id: I9a191da0ec6ac1 3ec6dd882b1723d 3686f9edc8c
Closes-Bug: #1840764