overcloudrc ends up with an invalid no_proxy
Bug #1854868 reported by
Alex Schultz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Low
|
Alex Schultz |
Bug Description
If the system no_proxy configuration contains spaces, the resulting overcloudrc file ends up being incorrectly generated.
# cat /etc/profile.
PROXY_ENABLED="yes"
export http_proxy="http://
export https_proxy="http://
export no_proxy=
Follows overcloudrc file after the deployment
# cat overcloudrc | grep proxy
export no_proxy=localhost, 127.0.0.1, myhost.com
Follows when I source the overcloudrc file.
source overcloudrc
bash: export: `127.0.0.1,': not a valid identifier
bash: export: `myhost.com': not a valid identifier
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/696985
Review: https:/