yahoo-eng-team team mailing list archive

[Blake Rouse <blake.rouse@xxxxxxxxxxxxx>]

This seems like a very strange thing that cloud-init should be doing.
Maybe for the first interface that MAAS brings up it makes since for
cloud-init to do, but all the other interfaces are brought up by the
MAAS commissioning scripts. That process is a direct process as well and
does not place any information in /etc/network/interfaces for Ubuntu to
even know that those IP addresses should be released.

Also their is the matter of getting this into cloud-init and having it
work across trusty+. It should be rather simple for the MAAS
commissioning script to inject a poweroff script that will be ran at the
very end of the shutdown process to release all IP addresses on
interfaces.

** Changed in: cloud-init
       Status: New => Invalid

** Changed in: maas
       Status: Incomplete => Triaged

-- 
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:
  Invalid
Status in MAAS:
  Triaged

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