cloud-init-dev team mailing list archive

[Jason Zions <jason.zions@xxxxxxxxxxxxx>]

Jason Zions has proposed merging ~jasonzio/cloud-init:disableIMDSnetcfg into cloud-init:master.

Commit message:
azure: Disable use of IMDS-derived metadata for network config

When a VM has multiple IP addresses associated with its NIC(s),
the metadata delivered by IMDS doesn't correctly indicate the
"primary" IP address to be used to communicate with the Azure
control plane, resulting in a provisioning failure.

Requested reviews:
  cloud-init commiters (cloud-init-dev)

For more details, see:
https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/364012

Interim fix for https://bugs.launchpad.net/cloud-init/+bug/1818302
while Azure fixes IMDS.
-- 
Your team cloud-init commiters is requested to review the proposed merge of ~jasonzio/cloud-init:disableIMDSnetcfg into cloud-init:master.

diff --git a/cloudinit/sources/DataSourceAzure.py b/cloudinit/sources/DataSourceAzure.py
index eccbee5..ea0b5c4 100644
--- a/cloudinit/sources/DataSourceAzure.py
+++ b/cloudinit/sources/DataSourceAzure.py
@@ -208,9 +208,10 @@ BUILTIN_DS_CONFIG = {
     },
     'disk_aliases': {'ephemeral0': RESOURCE_DISK_PATH},
     'dhclient_lease_file': LEASE_FILE,
-    'apply_network_config': True,  # Use IMDS published network configuration
+    'apply_network_config': False,  # Don't use IMDS published network config
 }
 # RELEASE_BLOCKER: Xenial and earlier apply_network_config default is False
+# Some very complex IMDS published network configs cause incorrect behavior
 
 BUILTIN_CLOUD_CONFIG = {
     'disk_setup': {