api-server container hard codes --noproxy in container arguments

Bug #2017107 reported by Tom Haddon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Medium
Unassigned

Bug Description

When bootstrapping Juju on Kubernetes, we noticed that the api-server container hard codes the following as part of the container args:

curl -sSf -o $gui/gui.tar.bz2 --retry 10 --noproxy 127.0.0.1,localhost,::1 'https://streams.canonical.com/juju/gui/gui/0.8.1/juju-dashboard-0.8.1.tar.bz2'

This means that if you're running in an environment where you have particular proxy settings (for instance http_proxy/https_proxy/no_proxy defined in /etc/environment) the no_proxy portion of that is being ignored.

Tom Haddon (mthaddon)
tags: added: canonical-is
tags: added: dashboard proxy
Revision history for this message
Juan M. Tirado (tiradojm) wrote :

What version of Juju is this one?

Changed in juju:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Joseph Phillips (manadart) wrote :
Revision history for this message
Tom Haddon (mthaddon) wrote :

This was in Juju 2.9.42. I can test on other versions if needed.

Revision history for this message
Ian Booth (wallyworld) wrote :

For now you can use the "--no-gui" arg to bootstrap to avoid this.

And in juju 3.0 and later, the gui is gone, replaced by the dashboard charm.

tags: added: 2.9
removed: dashboard
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.