Comment 17 for bug 1991261

Oh dear, I'm afraid I may have been barking up the wrong tree with this one...

As requested on IRC, I went to gather cloud-init collect-logs from a jammy instance and was surprised to find that, unlike last week it wasn't successfully "pingable" after the first boot. I wondered if I'd used the wrong image (release instead of .1 for instance), but no. It appears I've been seeing stale DNS records! Because my test images usually share a hostname (miss-piggy) and because I'm often just switching the card but not the Pi itself, it winds up with the same DHCP address (because dnsmasq typically attempts to use predictable addresses derived from the MAC). So it's just seeing the "miss-piggy" name from a prior reboot, with the same address...

So: my apologies for the invalid report! On the plus side, I re-tested the dsmode=local work-around with different names and confirmed it definitely sets things correct on first boot, so that change can go into kinetic (and future releases).

I *would* close this as invalid, but for the point about the documentation of set-hostname which could probably do with some clarification? And the possible confusion about NoCloud using dsmode=net? Anyway, I leave it to your best judgement!