Canonical Juju

  1. Bug #1782236
  2. Comment #0

Comment 0 for bug 1782236

Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote : juju-no-proxy variable is not applied due to legacy no-proxy value being auto-set by juju

It appears to be that "auto noproxy" behavior triggers an incorrect behavior with new juju-no-proxy value albeit the legacy one is set to an empty string.

juju model-config -m controller logging-config='<root>=ERROR;unit=TRACE;juju.worker.proxyupdater=TRACE'

juju model-config -m controller juju-http-proxy=http://10.10.101.2:8000 juju-https-proxy=http://10.10.101.2:8000 juju-no-proxy='localhost,127.0.0.1,10.10.10.0/24,10.10.101.0/24' http-proxy='' https-proxy="" no-proxy=""

machine-0.log on the controller machine:

2018-07-17 20:27:14 DEBUG juju.worker.proxyupdater proxyupdater.go:185 new legacy proxy settings proxy.Settings{Http:"", Https:"", Ftp:"", NoProxy:"10.10.101.19", AutoNoProxy:""}
2018-07-17 20:27:14 TRACE juju.worker.proxyupdater proxyupdater.go:213 setting snap proxy values: proxy.Settings{Http:"", Https:"", Ftp:"", NoProxy:"", AutoNoProxy:""}, "", ""

# on a controller machine
ip -4 -o -br a s
lo UNKNOWN 127.0.0.1/8
enp1s0 UP 10.10.101.19/24

juju status -m controller
Model Controller Cloud/Region Version SLA Timestamp
controller vmaas vmaas 2.4.1 unsupported 23:44:37+03:00

Machine State DNS Inst id Series AZ Message
0 started 10.10.101.19 xwqr38 xenial default Deployed

snap info juju | grep -P ' candidate'
  candidate: 2.4.1+2.4-7213ffe (4691) 63MB classic