b37ae4388c
In If6125cf7af84dd1b4fa869f13932c43ac013d443 we identified a few different minor issues, some syntax, and one concern over metadata and the data length. In this patch, we address final pass reviewer comments *and* shorten the interface ID values to more generic values which fullfill the named label/id value in the configuration drive schema, and are also values one could potentially use at some point down the road with vlans. Instead of "eth" as a prepended field name, we use "iface", since we can't have any value which really suggests a direct interface name mapping either. Change-Id: I637412591ae57a8591a1a948f54be56785a8a1e3 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
16 lines
879 B
YAML
16 lines
879 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue where a Nova, or other consumer attempting to send network
|
|
data to Ironic can send invalid network metadata which needs to
|
|
be replaced. Ironic now identifies the condition, and regenerates the network
|
|
metadata utilizing the attached VIF records. This results in some minor
|
|
data differences, such as Nova's internal VIF tap naming which is redundant,
|
|
and MTUs to be included in the Network data when they might not have been
|
|
included previously. More information about this bug can be found in
|
|
bug `2106073 <https://bugs.launchpad.net/ironic/+bug/2106073>`_. This logic
|
|
does *not* attempt to patch or modify configuration drive URLs which are
|
|
supplied by tools like Bifrost, which is unaffected by this issue.
|
|
This fix can be disabled by setting ``[conductor]disable_configdrive_check``
|
|
to ``True``.
|