From 60bbf85aa20cc38218123fb6fb7521268e3ac0f6 Mon Sep 17 00:00:00 2001 From: Gauvain Pocentek Date: Tue, 10 Mar 2020 12:46:17 +0100 Subject: Fix invalid test in cinder data migration script The extend_start.sh script for cinder-api uses an incorrect test to check if the MAX_NUMBER variable is set. This leads to a incorrect cinder-manage command being run if this variable is not set, making the database migration fail. This change fixes the test to properly use the MAX_NUMBER variable. Change-Id: Ie46da709db0de09a9cf641b3c154275282f213fc Closes-Bug: #1866827 (cherry picked from commit ff42ff20048ef3b7d2f8df04ada8ff4bf7b710e0) --- docker/cinder/cinder-api/extend_start.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docker/cinder') diff --git a/docker/cinder/cinder-api/extend_start.sh b/docker/cinder/cinder-api/extend_start.sh index cc0fd43f2..353983a95 100644 --- a/docker/cinder/cinder-api/extend_start.sh +++ b/docker/cinder/cinder-api/extend_start.sh @@ -9,7 +9,7 @@ if [[ "${!KOLLA_BOOTSTRAP[@]}" ]]; then fi if [[ "${!KOLLA_OSM[@]}" ]]; then - if [[ -z ${MAX_NUMBER} ]]; then + if [[ "${!MAX_NUMBER[@]}" ]]; then cinder-manage db online_data_migrations --max_count ${MAX_NUMBER} else cinder-manage db online_data_migrations -- cgit v1.2.3