apt-http-proxy being reset to bridge address

[Stuart Bishop]

Despite explicitly setting apt-http-proxy to another machine on my local network, bootstrap is pulling another value from somewhere or is choosing to rewrite it to the bridge address.

stub@aargh:~/.juju$ cat ~/.juju/environments.yaml
default: local

environments:
    # https://juju.ubuntu.com/docs/config-local.html
    local:
        type: local
        # agent-stream: devel

        apt-mirror: http://th.archive.ubuntu.com/ubuntu
        apt-http-proxy: http://192.168.1.201:8000/

        root-dir: ~/.local/juju
        default-series: trusty
        enable-os-refresh-update: false
        enable-os-upgrade: false
stub@aargh:~/.juju$ juju bootstrap
Bootstrapping environment "local"
Starting new instance for initial state server
Building tools to upload (1.22.0.1-vivid-amd64)
Installing Juju agent on bootstrap instance
Logging to /home/stub/.local/juju/cloud-init-output.log on remote host
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-stub-local)
Bootstrap complete
stub@aargh:~/.juju$ juju get-env apt-http-proxy
http://10.0.3.1:8000/

[Stuart Bishop (stub)]

2015-03-27 12:30:24 INFO juju.provider.local environprovider.go:46 opening environment "local"
2015-03-27 12:30:24 INFO juju.provider.local environprovider.go:112
Attribute "apt-http-proxy" is set to (http://10.0.3.1:8000/)

[Dimiter Naydenov (dimitern)]

This seems like fallout from fixing bug 1309207 with https://github.com/juju/juju/pull/1017 - the regexp used to detect localhost and swap it with the bridge IP (swapLocalhostForBridgeIP() in provider/local/environprovider.go) is too broad: the case "|[0:]+1|" exactly matches your case with http://192.168.1.201:8000/

[Aaron Bentley (abentley)]

Landed for 1.22 via https://github.com/juju/juju/pull/1972