cloud-init on azure with dual stack needs to add route-metric for dhcp6 also

Bug #1850308 reported by Dan Streetman on 2019-10-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Chad Smith

Bug Description

cloud-init on azure generates netplan yaml that includes dhcp4 with the dhcp4-overrides of route-metric, i.e.:

            dhcp4: true
                route-metric: 100

however netplan requires the same route-metric for dhcp4 and dhcp6 as networkd doesn't allow specifying separate metrics for 4 vs 6, so when azure is setup with dual-stack the netplan yaml is not valid for netplan, i.e.:

            dhcp4: true
                route-metric: 100
            dhcp6: true

which causes netplan to exit with error:

Stderr: ERROR: eth0: networkd requires that route-metric has the same value in both dhcp4_overrides and dhcp6_overrides

Tags: sts Edit Tag help

Related branches

Dan Streetman (ddstreet) on 2019-10-29
tags: added: sts
Ryan Harper (raharper) on 2019-10-29
Changed in cloud-init:
importance: Undecided → High
status: New → Triaged
Chad Smith (chad.smith) on 2019-10-31
Changed in cloud-init:
assignee: nobody → Chad Smith (chad.smith)
status: Triaged → In Progress

This bug is fixed with commit 02f07b66 to cloud-init on branch master.
To view that commit see the following URL:

Changed in cloud-init:
status: In Progress → Fix Committed
Chad Smith (chad.smith) on 2019-12-16
description: updated
description: updated

This bug is believed to be fixed in cloud-init in version 19.2-80. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers