apt-mirror does not override security.ubuntu.com for controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Similar with https:/
$ juju version
2.0-beta13-
$ cat config.yaml
default-series: xenial
agent-stream: devel
apt-mirror: http://
agent-metadata-url: http://
image-metadata-url: https:/
$ juju bootstrap --config config.yaml localhost lxd --debug
...
Attempting to connect to 10.0.8.153:22
2016-07-26 09:00:25 DEBUG juju.utils.ssh ssh.go:292 using OpenSSH ssh client
Warning: Permanently added '10.0.8.153' (ECDSA) to the list of known hosts.
sudo: unable to resolve host juju-ee9769-0: Connection timed out
Logging to /var/log/
Changing apt mirror to http://
Running apt-get update
...
[/var/log/
Cloud-init v. 0.7.7 finished at Tue, 26 Jul 2016 09:00:22 +0000. Datasource DataSourceNoCloud [seed=/
Err:1 http://
Temporary failure resolving 'security.
Get:2 http://
...
Get:21 http://
Fetched 10.3 MB in 1s (5698 kB/s)
Reading package lists...
W: Failed to fetch http://
W: Some index files failed to download. They have been ignored, or old ones used instead.
Changed in juju-core: | |
status: | Incomplete → New |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.0-rc1 |
Changed in juju-core: | |
milestone: | 2.0-rc1 → 2.0.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.0 → none |
milestone: | none → 2.0.0 |
Changed in juju: | |
milestone: | 2.0.0 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
We do look into all location known to Juju. This means trying to connect to all defaults.
In most case, though, we try to connect to user-specified locations first. It does not appear to be the case here.
Did you bootstrap successfully?