Agent fails to download tools from Juju controller with multiple network interfaces
Bug #1626492 reported by
Tytus Kurek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Undecided
|
Unassigned | ||
juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
1.25 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I have Juju (1.25.6-
10.255.32.13/24
10.255.33.13/24
10.255.34.13/24
10.255.35.13/24
10.255.8.13/21
172.18.252.12/23
176.106.116.13/24
When trying to deploy anything the 10.255.32.13 IP addresses is being used in the URL to download Juju tools, probably because alphabetically it's the first. As all nodes are connected to these networks in the same way there's no problem with deploying on hosts, but when it comes to containers which are bridged to 172.18.252.0/23 network only they fail to download Juju tools.
Attached is the output of "/var/log/
To post a comment you must log in.
1.25 is in Critical-bugs only mode.
We need a confirmation that you are experiencing the same failure on Juju 2. Could you please try 2.0-rc1?