networking comes up before hostname is set

This bug was originally filed in Launchpad as [LP: #1739516](https://bugs.launchpad.net/cloud-init/+bug/1739516)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2017-12-21T02:05:24.786441+00:00

date_fix_committed = None

date_fix_released = None

id = 1739516

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1739516

milestone = None

owner = mwhudson

owner_name = Michael Hudson-Doyle

private = False

status = confirmed

submitter = mwhudson

submitter_name = Michael Hudson-Doyle

tags = []

duplicates = []

_Launchpad user **Michael Hudson-Doyle(mwhudson)** wrote on 2017-12-21T02:05:24.786441+00:00_

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.