IMAGE-1179: cloud-init should be able to reconfigure network on each boot


Issue Type:Improvement
Priority:3 - Elevated
Created at:2018-04-20T15:13:42.804Z
Updated at:2020-04-02T13:57:32.003Z


Created by:Former user
Reported by:Former user
Assigned to:Former user


Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2020-04-02T13:57:31.992Z)

Related Issues




Due to kvm's use of dhcp, it has a way to automatically pick up network configuration on each boot.  For feature parity in bhyve,  cloud-init needs to be able to reconfigure the network on each boot.

Implementation plan

Support for a boolean customer metadata property, maintain_network will be added.  If this is not present or set to any value other than false, the network will be reconfigured on every boot.


This value has no impact on first boot.

This value is only respected by HVM images that contain and use a version of cloud-init that supports the maintain_network metadata item.  This is expected to first exist in an update to cloud-init 18.3 or later.

Legacy cloud-init found in debian 8 and centos 6 will not have the ability to control this setting - cloud-init will always be in control of network configuration.


Comment by Former user
Created at 2018-04-20T17:51:22.348Z

The cloud-init changes are tracked at

Comment by Former user
Created at 2018-04-24T17:59:38.126Z

This is currently in a holding pattern due to concern about how this fix will interact with eventual network hotplug.  The hotplug proposal was written in January 2018 with no visible progress since then.

Comment by Former user
Created at 2018-05-14T21:57:14.843Z

There seems to be agreement that this is worthwhile to approach while hotplug is fleshed out. I received review feedback and things are moving along again.

Comment by Former user
Created at 2018-06-05T16:39:44.982Z

Bumped priority to match OS-6965, which was closed as a dup of this.

Comment by Former user
Created at 2018-07-03T14:52:43.886Z

This work has been completed for all non-Ubuntu images.

For Ubuntu, the prerequisite work has just landed.

Comment by Former user
Created at 2019-09-25T16:34:56.025Z

Merge request updated for cloud-init:

This will eventually allow it to make its way into ubuntu certified images

Comment by Former user
Created at 2019-10-31T20:46:37.630Z

This should make it into cloud-init 19.3.

Comment by Former user
Created at 2019-11-06T14:34:19.752Z

cloud-init 19.3 was released yesterday. History suggests that it will find its way into Ubuntu 18.04 updates soon.

Comment by Former user
Created at 2019-12-17T18:22:58.457Z

Per the cloud-init mailing list:

Canonical has just finished Stable Release Update (SRU) validation of
cloud-init version 19.3.41 into Ubuntu Xenial, Bionic, Disco and Eoan. It is
currently available in the <ubuntu-series>-updates repositories and will
make it into certified cloud images in the next few days.

The changelog provided in this update can be seen in the package changelog
or in the following process bug:

Thank you all for your contributions to this version of cloud-init.

This means that apt update; apt-upgrade cloud-init should allow existing and Ubuntu 16.04 and 18.40 instances to begin to use this feature.