Public bug reported:
When boot with libvirt a disk image that has been installed with
subiquity which has the workaround for bug 1737630 applied, i.e.
networkd starts automatically, I cannot ping the VM by hostname from the
host.
I think this is because the networking has come up before the hostname
is set, so the hostname is not sent along with the DHCP request to
libvirt's dnsmasq and so that dnsmasq cannot answer lookups for the
hostname. If I run "netplan apply" on the vm, enough things are
apparently restarted that DHCP happens again and I can ping the vm by
hostname from the host.
I'm not completely sure I have diagnosed this correctly and certainly
don't know how to fix it.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1739516
Title:
networking comes up before hostname is set
Status in cloud-init:
New
Bug description:
When boot with libvirt a disk image that has been installed with
subiquity which has the workaround for bug 1737630 applied, i.e.
networkd starts automatically, I cannot ping the VM by hostname from
the host.
I think this is because the networking has come up before the hostname
is set, so the hostname is not sent along with the DHCP request to
libvirt's dnsmasq and so that dnsmasq cannot answer lookups for the
hostname. If I run "netplan apply" on the vm, enough things are
apparently restarted that DHCP happens again and I can ping the vm by
hostname from the host.
I'm not completely sure I have diagnosed this correctly and certainly
don't know how to fix it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1739516/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
