Controller bootstrap fails in environment using proxy to reach the internet even when the juju proxy config is passed with --config option

[Kamal Bhaskar]

Problem:

Juju controller bootstrap fails in an environment that needs proxy to reach the internet, even when the juju proxy configurations are passed as a config file using --config option.

Juju version: 3.5.4

Cloud: MAAS

Steps to reproduce:

Try to bootstrap a controller using below command in an environment with proxy for internet access:

juju bootstrap --config=./bootstrap-juju-3_5.yaml <maas-cloud> --bootstrap-base=ubuntu@22.04 --to <machine-constraints> <NEW_CTRL>

# where "bootstrap-juju-3_5.yaml" contains:

juju-http-proxy: http://<IP>:<PORT>/
juju-https-proxy: http://<IP>:<PORT>/
juju-no-proxy: <PRIVATE-SUBNET-CIDR>
apt-http-proxy: http://<IP>:<PORT>/
apt-https-proxy: http://<IP>:<PORT>/
snap-http-proxy: http://<IP>:<PORT>/
snap-https-proxy: http://<IP>:<PORT>/
bootstrap-timeout: 3600

Observations:

It ignores the proxy config during the bootstrap but after the bootstrap is completed it sets up the controller's proxy model-config appropriately.
Also, explained in [1], used below workaround to make it work for now:

- Downloaded charm:

juju download juju-controller --channel 3.5/stable --base ubuntu@22.04

- Passed the downloaded file to "juju bootstrap" command:

--controller-charm-path=./juju-controller_r105.charm

References:

[1] https://discourse.charmhub.io/t/juju-controller-bootstrap-fails-because-it-doesnt-use-proxy-even-if-set/9979