Browse code

Fix glance standalone when tls-proxy is disabled

We always want to start glance on the internal port now,
regardless of whether or not tls-proxy is in use, because we
write_local_proxy_http_config() for the standalone case.

Change-Id: I47dea645d4a852e02e25af0e1df9c28fec92c42a
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>

Dan Smith authored on 2020/07/18 02:14:14
Showing 1 changed files
... ...
@@ -252,6 +252,7 @@ function configure_glance {
252 252
     else
253 253
         write_local_proxy_http_config glance "http://$GLANCE_SERVICE_HOST:$GLANCE_SERVICE_PORT_INT" "/image"
254 254
         iniset $GLANCE_API_CONF DEFAULT bind_host $GLANCE_SERVICE_LISTEN_ADDRESS
255
+        iniset $GLANCE_API_CONF DEFAULT bind_port $GLANCE_SERVICE_PORT_INT
255 256
         iniset $GLANCE_API_CONF DEFAULT workers "$API_WORKERS"
256 257
     fi
257 258
 }