Correct case pattern handling in MOD_WSGI checks
If we've got two identical patterns one of them needs to fall through or have them both in the same block. It appears there was some merge confusion withf42d6c8a8dand5f8b3cb631This tries to get the correct the original intent: flat out disable for ceilometer and disable depending on branch for keystone. Change-Id: I9e5e792ef43f9a3cdc0b84c73f27b62109ed5d31
This commit is contained in:
@@ -330,10 +330,6 @@ EOF
|
||||
;&
|
||||
"stable/juno")
|
||||
echo "KEYSTONE_USE_MOD_WSGI=False" >> "$localrc_file"
|
||||
echo "CEILOMETER_USE_MOD_WSGI=False" >> "$localrc_file"
|
||||
;;
|
||||
"stable/kilo")
|
||||
echo "CEILOMETER_USE_MOD_WSGI=False" >> "$localrc_file"
|
||||
;;
|
||||
"stable/kilo")
|
||||
# while both juno and kilo can run under wsgi, they
|
||||
@@ -345,6 +341,7 @@ EOF
|
||||
echo "KEYSTONE_USE_MOD_WSGI=False" >> "$localrc_file"
|
||||
;;
|
||||
esac
|
||||
echo "CEILOMETER_USE_MOD_WSGI=False" >> "$localrc_file"
|
||||
fi
|
||||
|
||||
if [[ "$DEVSTACK_GATE_TEMPEST_LARGE_OPS" -eq "1" ]]; then
|
||||
|
||||
Reference in New Issue
Block a user