At the moment, no_proxy variable is evaluated separately for docker
daemon and for swarm-manager container running in docker. Evaluated
value for swarm-manager is not getting into cloud-init script, because
$NODE_PROXY token is getting replaced by Heat str_replace function.
This commit is intended to unify NO_PROXY evaluation and also fix the
issue with swarm-manager.
Reviewed: https:/ /review. openstack. org/457806 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=35dc923d662 13edebf7db122dd 929d79a8eb4cf7
Committed: https:/
Submitter: Jenkins
Branch: master
commit 35dc923d66213ed ebf7db122dd929d 79a8eb4cf7
Author: Michael Tupitsyn <email address hidden>
Date: Mon Apr 17 15:39:45 2017 -0700
Fix no_proxy evaluation for Swarm clusters
At the moment, no_proxy variable is evaluated separately for docker
daemon and for swarm-manager container running in docker. Evaluated
value for swarm-manager is not getting into cloud-init script, because
$NODE_PROXY token is getting replaced by Heat str_replace function.
This commit is intended to unify NO_PROXY evaluation and also fix the
issue with swarm-manager.
Related-Bug: #1647815 cae308bf7b61447 6b71b81fa01
Related-Bug: #1632698
Related-Bug: #1660562
Change-Id: I336024265008b6