If we start keystone with an SSL endpoint then the curl check to see if
it is running will fail because it cannot create a secure connection.
This check can be done insecurely as all we care about is that the
service has started.
Change-Id: I826753d4d46e9956f443110029346bc70282951a
| ... | ... |
@@ -424,7 +424,7 @@ function start_keystone() {
|
| 424 | 424 |
fi |
| 425 | 425 |
|
| 426 | 426 |
echo "Waiting for keystone to start..." |
| 427 |
- if ! timeout $SERVICE_TIMEOUT sh -c "while ! curl --noproxy '*' -s $KEYSTONE_AUTH_PROTOCOL://$SERVICE_HOST:$service_port/v$IDENTITY_API_VERSION/ >/dev/null; do sleep 1; done"; then |
|
| 427 |
+ if ! timeout $SERVICE_TIMEOUT sh -c "while ! curl --noproxy '*' -k -s $KEYSTONE_AUTH_PROTOCOL://$SERVICE_HOST:$service_port/v$IDENTITY_API_VERSION/ >/dev/null; do sleep 1; done"; then |
|
| 428 | 428 |
die $LINENO "keystone did not start" |
| 429 | 429 |
fi |
| 430 | 430 |
|