yahoo-eng-team team mailing list archive

[Adam Niedzwiecki <1926026@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Attachment added: "cloud-init.tar.gz"
   https://bugs.launchpad.net/bugs/1926026/+attachment/5491852/+files/cloud-init.tar.gz

-- 
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/1926026

Title:
  Updated default-network fails to sync up with DHCP server

Status in cloud-init:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1926026/+subscriptions