[local] juju-create hard-coded to use 192.168.122.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
High
|
Clint Byrum | ||
juju (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
On up to date precise, if I am running libvirt with the non-default network of 192.168.123.1, juju-create does not honor this. It is hard-coded to use:
cat <<EOF >> /etc/apt/
Acquire::http { Proxy "http://
EOF
...
cat <<EOF > /etc/resolvconf
nameserver 192.168.122.1
EOF
cat <<EOF > /etc/resolvconf
nameserver 192.168.122.1
EOF
...
It would be best if this could be autodetected. An alternative would be to make this configurable by sourcing a file since juju-create is a shell script.
As a workaround I can edit /usr/share/
description: | updated |
Changed in juju (Ubuntu): | |
importance: | Undecided → Medium |
importance: | Medium → High |
description: | updated |
Changed in juju (Ubuntu): | |
status: | New → Confirmed |
status: | Confirmed → Triaged |
Changed in juju: | |
importance: | Undecided → High |
summary: |
- juju-create hard-coded to use 192.168.122.1 + [local] juju-create hard-coded to use 192.168.122.1 |
tags: | added: local |
Changed in juju: | |
status: | New → Confirmed |
Changed in juju: | |
milestone: | none → galapagos |
Changed in juju: | |
milestone: | galapagos → honolulu |
Part of moving to using the cloud images for LXC will be to ditch the libvirt tie-in and use lxc's networking instead.