50ced3a3fa
In the early days of the neutron network interface, we had a hard launch failure added to prevent ironic.conf from having a neutron network configuration which was not valid when the neutron network interface was in use. But as time has moved on, these settings became node-settable, and ironic configuration largely became mutable as well, so they can always be added after the process has been launched. But we kept the error being returned. Which doesn't make sense now that it can always be back-filled into a working state or just entirely be "user supplied" via the API by an appropriate user. Closes-Bug: 2054728 Change-Id: I33e76929ca9bf7869b3b4ef4d6501e692cf0a922
10 lines
471 B
YAML
10 lines
471 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue where the conductor service would fail to launch when
|
|
the ``neutron`` network_interface setting was enabled, and no global
|
|
``cleaning_network`` or ``provisioning_network`` is set in `ironic.conf.`
|
|
These settings have long been able to be applied on a per-node basis via
|
|
the API. As such, the service can now be started and will error on node
|
|
validation calls, as designed for drivers missing networking parameters.
|