yahoo-eng-team team mailing list archive

[Mike Pontillo <mike.pontillo@xxxxxxxxxxxxx>]

The MAAS team discussed this today; we feel like since cloud-init is
responsible for configuring the interfaces to DHCP, and is responsible
for sending the last status message to the network before powering off
the system, cloud-init should be responsible for running "dhclient -r
<interface>" for each interface it configured for DHCP.

We would most likely want a boolean we could set in the cloud-init
configuration which would cause this behavior to occur; we would only
want to release the IP address when we're booting the system
ephemerally. It seems possible that we would inadvertently cause
regressions with some integrations if cloud-init unconditionally
released its IP addresses. What do you think?

** Also 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/1577960

Title:
  [2.0b4] After commissioning, subnet lists 'observed' IP address for
  machines

Status in cloud-init:
  New
Status in MAAS:
  Incomplete

Bug description:
  I commissioned a whole bunch of machines, and after it compelted, MAAS
  showed 'Machines' with 'Observed' IP addresses but machines are now
  off.

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