Description of problem: At the end of overcloud deployment, the process tries to write into the overcloudrc the environment no_proxy configuration but it forgets double quoting the entire string. Follows my customer example # cat /etc/profile.d/proxy.sh PROXY_ENABLED="yes" export http_proxy="http://hubsekiproxy.rnd.ericsson.se:8080" export https_proxy="http://hubsekiproxy.rnd.ericsson.se:8080" export no_proxy="localhost, 127.0.0.1, 10.209.97.86, .seki.rnd.ericsson.se, .rnd.ki.sw.ericsson.se, .rnd.ericsson.se, ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se" Follows overcloudrc file after the deployment # cat overcloudrc | grep proxy export no_proxy=localhost, 127.0.0.1, 10.209.97.86, .seki.rnd.ericsson.se, .rnd.ki.sw.ericsson.se, .rnd.ericsson.se, ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se,ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se,10.209.97.100 Follows when I source the overcloudrc file. source overcloudrc bash: export: `127.0.0.1,': not a valid identifier bash: export: `10.209.97.86,': not a valid identifier bash: export: `.seki.rnd.ericsson.se,': not a valid identifier bash: export: `.rnd.ki.sw.ericsson.se,': not a valid identifier bash: export: `.rnd.ericsson.se,': not a valid identifier bash: export: `ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se,ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se,10.209.97.100': not a valid identifier Version-Release number of selected component (if applicable): OSP13z1 Actual results: export no_proxy=localhost, 127.0.0.1, 10.209.97.86, .seki.rnd.ericsson.se, .rnd.ki.sw.ericsson.se, .rnd.ericsson.se, ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se,ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se,10.209.97.100 Expected results: export no_proxy="localhost, 127.0.0.1, 10.209.97.86, .seki.rnd.ericsson.se, .rnd.ki.sw.ericsson.se, .rnd.ericsson.se, ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se,ctrl-vran-redhat011.vran.edn.ki.sw.ericsson.se,10.209.97.100"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0760