| 2016-07-11 10:42:03 |
Simon Davy |
bug |
|
|
added bug |
| 2016-07-11 20:44:52 |
Stéphane Graber |
affects |
lxd (Ubuntu) |
cloud-init (Ubuntu) |
|
| 2016-07-14 09:44:41 |
Simon Davy |
description |
When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the initial dhcp is always the hostname 'ubuntu', and this is recorded in the dnsmasq's dhcp leases file.
Presumably the dhcp is done before the container's hostname is set. A restart or dhcp renew seems to put the correct container name in the leases file.
This is a problem when using the dnsmasq for local dns resolving for *.lxd, which is the standard way of doing host dns for containers, as new containers are not dns addressable with a restart or renew.
Is there anyway get the correct hostname in the initial dhcp? Or maybe renew after setting the hostname? |
When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the initial dhcp is always the hostname 'ubuntu', and this is recorded in the dnsmasq's dhcp leases file.
Presumably the dhcp is done before the container's hostname is set. A restart or dhcp renew seems to put the correct container name in the leases file.
This is a problem when using the dnsmasq for local dns resolving for *.lxd, which is the standard way of doing host dns for containers, as new containers are not dns addressable without a restart or renew.
Is there anyway get the correct hostname in the initial dhcp? Or maybe renew after setting the hostname? |
|
| 2016-07-27 11:23:16 |
Jon Grimm |
bug |
|
|
added subscriber Jon Grimm |
| 2016-07-27 12:15:16 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2016-07-27 17:11:10 |
Scott Moser |
description |
When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the initial dhcp is always the hostname 'ubuntu', and this is recorded in the dnsmasq's dhcp leases file.
Presumably the dhcp is done before the container's hostname is set. A restart or dhcp renew seems to put the correct container name in the leases file.
This is a problem when using the dnsmasq for local dns resolving for *.lxd, which is the standard way of doing host dns for containers, as new containers are not dns addressable without a restart or renew.
Is there anyway get the correct hostname in the initial dhcp? Or maybe renew after setting the hostname? |
When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the initial dhcp is always the hostname 'ubuntu', and this is recorded in the dnsmasq's dhcp leases file.
Presumably the dhcp is done before the container's hostname is set. A restart or dhcp renew seems to put the correct container name in the leases file.
This is a problem when using the dnsmasq for local dns resolving for *.lxd, which is the standard way of doing host dns for containers, as new containers are not dns addressable without a restart or renew.
Is there anyway get the correct hostname in the initial dhcp? Or maybe renew after setting the hostname?
Related Bugs:
* LXC/LXD Issue https://github.com/lxc/lxd/issues/2244 |
|
| 2016-08-03 21:21:16 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2016-08-03 21:23:00 |
Bjorge Dijkstra |
bug |
|
|
added subscriber Bjorge Dijkstra |
| 2016-09-02 13:41:28 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
| 2016-09-02 13:41:30 |
Scott Moser |
cloud-init: importance |
Undecided |
Low |
|
| 2016-09-02 13:41:33 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Low |
|
| 2018-01-11 08:45:51 |
Claudio Gardini |
bug task added |
|
juju |
|
| 2018-01-30 23:59:19 |
Anastasia |
juju: status |
New |
Triaged |
|
| 2018-01-30 23:59:30 |
Anastasia |
juju: importance |
Undecided |
Medium |
|
| 2018-01-31 04:17:12 |
Anastasia |
juju: status |
Triaged |
Invalid |
|
| 2018-01-31 14:31:31 |
Felipe Reyes |
bug |
|
|
added subscriber Felipe Reyes |
| 2018-02-01 15:53:10 |
Chris Gregan |
tags |
|
cdo-qa-blocker cpe-onsite |
|
| 2018-02-01 15:53:22 |
Chris Gregan |
bug |
|
|
added subscriber Canonical Field High |
| 2018-02-01 18:25:14 |
David Britton |
bug watch added |
|
https://github.com/lxc/lxd/issues/2244 |
|
| 2018-02-01 23:53:59 |
David Britton |
cloud-init (Ubuntu): status |
Confirmed |
Won't Fix |
|
| 2018-02-01 23:54:02 |
David Britton |
cloud-init: status |
Confirmed |
Won't Fix |
|
| 2023-05-10 14:27:31 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2691 |
|
