apply networking only on first instance boot

Bug #1571004 reported by Scott Moser on 2016-04-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Scott Moser

Bug Description

Currently cloud-init is applying networking on every boot.
On 'local' data sources that provide 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.

Related branches

Scott Moser (smoser) wrote :

The fix is to only apply when we have not re-loaded a datasource found in the cache.

Scott Moser (smoser) on 2016-04-15
Changed in cloud-init:
assignee: nobody → Scott Moser (smoser)
importance: Undecided → Medium
status: New → In Progress
Scott Moser (smoser) on 2016-06-03
Changed in cloud-init:
status: In Progress → Fix Committed
Joshua Harlow (harlowja) on 2016-07-21
Changed in cloud-init:
milestone: none → 0.7.7
Scott Moser (smoser) on 2016-08-10
Changed in cloud-init:
status: Fix Committed → Fix Released
Scott Moser (smoser) on 2018-04-20
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers