Fix remote dcmanager access

Dcmanager needs another environment variable set in order to properly
work with the remote setup.

The variable is OS_ENDPOINT_TYPE and must be set to "publicURL" for
any kind of remote access. Unless otherwise specified, dcmanager
defaults to "internalURL".

The issue only affect dcmanager, as other platform commands (system
and fm) work without this variable set, but also don't seem to be
affected in any way when this variable is configured to "publicURL".

Change-Id: Ic70de40ff169d07800f9ee42f744b12768dc70ac
Closes-bug: 1869258
Signed-off-by: Stefan Dinescu <stefan.dinescu@windriver.com>
This commit is contained in:
Stefan Dinescu 2020-03-27 15:20:36 +02:00
parent 6c6f0b0b18
commit 8bf932a368
1 changed files with 9 additions and 1 deletions

View File

@ -38,7 +38,15 @@ OS_AUTH_URL OS_USERNAME OS_INTERFACE OS_PROJECT_DOMAIN_NAME
OS_AUTH_TYPE
EOF
COMMAND_ENV=""
# We initialize the environment variable list with the OS_ENDPOINT_TYPE set
# "publicURL" because dcmanager defaults to "internalURL" if not overridden
# by a parameter to the command itself or by the environment variable.
# For remote access the endpoint-type must always be publicURL, but the
# environment variable is not part of the set of variables present in the
# platform RC file downloaded from Horizon.
# In order for dcmanager to work properly, we manually set this variable
# to the correct value.
COMMAND_ENV="-e OS_ENDPOINT_TYPE=publicURL"
for exp in $EXPORTS; do
# If variable is not defined, don't pass it over to the container