diff options
| author | Slawek Kaplonski <skaplons@redhat.com> | 2022-09-02 15:58:50 +0200 |
|---|---|---|
| committer | Sylvain Bauza <sbauza@redhat.com> | 2022-11-29 15:12:24 +0000 |
| commit | 6bdc79af30151f683c0f462bc6c69da30ebcbcf9 (patch) | |
| tree | 755598a9f8a5fc1d1cee56be886b0169d156b48b /releasenotes | |
| parent | 0bab2e5a882235bfd41d2bce86db9885fd0b81b2 (diff) | |
| download | nova-6bdc79af30151f683c0f462bc6c69da30ebcbcf9.tar.gz | |
Don't provide MTU value in metadata service if DHCP is enabled
For networks with subnets with enabled DHCP service don't provide
mtu value in the metadata. That way cloud-init will not configure it
"statically" in e.g. netplan's config file and guest OS will use MTU
value provided by the DHCP service.
Closes-Bug: #1899487
Change-Id: Ib775c2210349b72b3dc033554ac6d8b35b8d2d79
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/Do-not-send-mtu-value-in-metadata-for-networks-with-enabled-dhcp-641506f2a13b540f.yaml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/releasenotes/notes/Do-not-send-mtu-value-in-metadata-for-networks-with-enabled-dhcp-641506f2a13b540f.yaml b/releasenotes/notes/Do-not-send-mtu-value-in-metadata-for-networks-with-enabled-dhcp-641506f2a13b540f.yaml new file mode 100644 index 0000000000..b5232f5ea2 --- /dev/null +++ b/releasenotes/notes/Do-not-send-mtu-value-in-metadata-for-networks-with-enabled-dhcp-641506f2a13b540f.yaml @@ -0,0 +1,5 @@ +--- +other: + - | + For networks which have any subnets with enabled DHCP, MTU value is not send + in the metadata. In such case MTU is configured through the DHCP server. |