Updated default-network fails to sync up with DHCP server

[Adam Niedzwiecki]

Following #1925454, I have modified default-network file - deleting a line optional: true, yet to no avail, still no DHCP lease from the MK router.

I shall get the IP 192.168.53.3, yet Ubuntu gets assigned next IP in the range, like 192.168.53.4 (or 192.168.53.5), and only after restart somehow the machine gets expected 192.168.53.3, which strangely enough is not showing up in DHCP Leases, but in ARP connections.

Log files attached..

Please advise..why my setup is not working with the Mikrotik's DHCP.

Thanks.

[Paride Legovini (paride)]

Thank you for taking the time to report this bug and helping to make cloud-init better.

Since it seems likely to me that this is a local configuration problem, rather than a bug in coud-init, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: https://cloudinit.readthedocs.io/en/21.1/topics/faq.html (How do I get help?).

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[Adam Niedzwiecki (aniecki)]

Thanks for the input.
This could well be as described. No time, no test hardware, and no skills to test it thoroughly.
Simply it does not work for me with the first init. I will raise the ticket with Mikrotik community, perhaps they provide some input too.

[Launchpad Janitor (janitor)]

[Expired for cloud-init because there has been no activity for 60 days.]

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3872