2019-10-29 12:44:43 |
Dan Streetman |
bug |
|
|
added bug |
2019-10-29 12:48:23 |
Dan Streetman |
tags |
|
sts |
|
2019-10-29 15:09:14 |
Joshua Powers |
bug |
|
|
added subscriber Joshua Powers |
2019-10-29 18:58:59 |
Ryan Harper |
cloud-init: importance |
Undecided |
High |
|
2019-10-29 18:58:59 |
Ryan Harper |
cloud-init: status |
New |
Triaged |
|
2019-10-31 20:08:00 |
Chad Smith |
cloud-init: assignee |
|
Chad Smith (chad.smith) |
|
2019-10-31 20:08:02 |
Chad Smith |
cloud-init: status |
Triaged |
In Progress |
|
2019-10-31 20:12:06 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/374994 |
|
2019-11-04 22:11:42 |
Server Team CI bot |
cloud-init: status |
In Progress |
Fix Committed |
|
2019-12-16 16:35:53 |
Chad Smith |
description |
cloud-init on azure generates netplan yaml that includes dhcp4 with the dhcp4-overrides of route-metric, i.e.:
dhcp4: true
dhcp4-overrides:
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
dhcp4-overrides:
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 |
cloud-init on azure generates netplan yaml that includes dhcp4 with the dhcp4-overrides of route-metric, i.e.:
dhcp4: true
dhcp4-overrides:
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
dhcp4-overrides:
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
LP: #123 |
|
2019-12-16 16:36:29 |
Chad Smith |
description |
cloud-init on azure generates netplan yaml that includes dhcp4 with the dhcp4-overrides of route-metric, i.e.:
dhcp4: true
dhcp4-overrides:
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
dhcp4-overrides:
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
LP: #123 |
cloud-init on azure generates netplan yaml that includes dhcp4 with the dhcp4-overrides of route-metric, i.e.:
dhcp4: true
dhcp4-overrides:
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
dhcp4-overrides:
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 |
|
2019-12-19 22:57:58 |
Chad Smith |
cloud-init: status |
Fix Committed |
Fix Released |
|
2023-05-12 01:13:44 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/3485 |
|
2023-05-17 12:47:33 |
Dan Streetman |
removed subscriber Dan Streetman |
|
|
|