*** This bug is a duplicate of bug 1607964 ***
https://bugs.launchpad.net/bugs/1607964
The superseded bug has more information.
** This bug has been marked a duplicate of bug 1607964
juju2, maas2, lxd containers started with wrong IP, rely on dhclient to
switch things
--
You received
By the way, these test scripts easily reproduce the issue:
https://github.com/pontillo/ubuntu-virt-bootstrap
You would just do:
./fetch
./verify
./create xenial xenial
Wait a little while for DHCP, then:
./vdig xenial
(comes up blank)
./vdig ubuntu
(has the 'xenial' VM's IP address.)
I hit this when writing some scripts to provision the Xenial cloud image
using a virtual CD-ROM data source. I would have expected that cloud-
init set the hostname before configuring DHCP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574963
Title:
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574963
Title:
juju2 lxd launch hostname reverse lookup inconsistent
To
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1574963
Title:
juju2 lxd launch hostname reverse lookup
This is solvable in cloud-init, and it would not be terribly invasive
for the lxc datasource (nocloud) as that is "local". For other
datasources that use the network, its more complex at least for now as
getting the hostname would mean dhcp on the network interface and thus
advertising 'ubuntu'.
This is solvable in cloud-init, and it would not be terribly invasive
for the lxc datasource (nocloud) as that is "local". For other
datasources that use the network, its more complex at least for now as
getting the hostname would mean dhcp on the network interface and thus
advertising 'ubuntu'.
** Description changed:
juju2 beta 5 on xenial:
When new lxd containers are launched on the local provider
a) the PTR record initially points to 'ubuntu.lxd' (not the machine name)
b) After launching another container, it points to nothing -- the second
container gets 'ubuntu.lxd'
This is a cloud-init problem I think.
Basically when the container first starts it's got the default hostname
from the image "ubuntu", then it runs dhclient to get an IP, that
dhclient calls sends the hostname to dnsmasq "ubuntu" at that point,
then cloud-init runs and sets the right hostname,
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574963
Title:
juju2 lxd launch hostname reverse lookup inconsistent
To
11 matches
Mail list logo
