c4f3abe22e
The commit b2e7de79df , which was merged
during Train cycle, introduced a few new parameters to support multi
interface driver, but the following two parameters are already declared
in the corresponding agent classes and trigger duplicate resource
declaration when these classes are used in a single manifest.
- dhcp_broadcast_reply
- interface_driver
This change allows users to workaround the problem. Details are
documented in the release note.
Closes-Bug: #1987460
Change-Id: I993523dc7f0ec8ad90a50d049dc0f5ccf9f2b191
15 lines
608 B
YAML
15 lines
608 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`Bug #1987460 <https://bugs.launchpad.net/puppet-neutron/+bug/1987460>`_:
|
|
Previously the ``neutron::agents::ml2::mlnx`` class causes duplicate
|
|
resources when used with the ``neutron::agents::dhcp`` class or
|
|
the ``neutron::agents::l3`` class. Now it is possible to workaround
|
|
the error by implementing the following mitigation.
|
|
|
|
- Include the ``neutron::agents::ml2::mlnx`` class AFTER
|
|
the ``neutron::agents::dhcp`` class or the ``neutron::agents::l3``
|
|
|
|
- Set the ``interface_driver`` parameter and the ``dhcp_broadcast_reply``
|
|
parameter consistently.
|