71481ac483
Generic way to configure clean step priorites feature ( https://review.opendev.org/c/openstack/ironic/+/744117 ) enabled support for customising clean step priorities for any clean step by setting a configuration option. However, due to an error in code, it was not possible to use this feature to enable/disable steps entirely using this option as overrides were applied too late, after the disabled steps were already filtered out. This change fixes this error, making it possible to use step priority override configuration option to enable/disable steps as required. Story: 2009105 Change-Id: If3c01e6e4e8cedfe053e78fab9632bfff3682b06
10 lines
431 B
YAML
10 lines
431 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Resolve issue where ``[conductor]clean_step_priority_override`` values
|
|
are applied too late, after disabled steps have been already filtered out.
|
|
With this change, priority overrides are applied prior to filtering out
|
|
disabled steps, so that this configuration option can use used to enable
|
|
or disable steps (in particular clean steps) in addition to changing
|
|
priorities they are run with.
|