← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1571004] [NEW] apply networking only on first instance boot

 

Public bug reported:

Currently cloud-init is applying networking on every boot.
On 'local' data sources that provides network information this is great.
On any other datasource:
  * local datasource without networking info
  * network based datasource

then the fallback networking is rendered on every boot.
In the scenario:
 a.) boot instance
 b.) fallback networking picks eth0.cfg and that is fine
 c.) attach network device
 d.) reboot

things can get hairy.

The suggested change is to only apply the networking configuration once per instance.
This is less dynamic and less surprising.

ie, if a user modifies /etc/network/interfaces.d/my.cfg and adds to or
improves on the fallback (or unconfigures the fallback) then their
changes might not interact well.

** 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/1571004

Title:
  apply networking only on first instance boot

Status in cloud-init:
  New

Bug description:
  Currently cloud-init is applying networking on every boot.
  On 'local' data sources that provides network information this is great.
  On any other datasource:
    * local datasource without networking info
    * network based datasource

  then the fallback networking is rendered on every boot.
  In the scenario:
   a.) boot instance
   b.) fallback networking picks eth0.cfg and that is fine
   c.) attach network device
   d.) reboot

  things can get hairy.

  The suggested change is to only apply the networking configuration once per instance.
  This is less dynamic and less surprising.

  ie, if a user modifies /etc/network/interfaces.d/my.cfg and adds to or
  improves on the fallback (or unconfigures the fallback) then their
  changes might not interact well.

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


Follow ups