87e68256b6
Operators should be able to choose if they wish to fallback when a disk based secure erase operation fails. Adds a configuration option to be passed to the agent during cleaning operations in order to allow that decision to prevent failed secure erase operations from causing the node to go into CLEANFAIL state by enabling fallback logic. Change-Id: I13c0fef3a6aa1903bfe1f54ba4fafbeadd673666 Closes-Bug: #1536695
17 lines
687 B
YAML
17 lines
687 B
YAML
---
|
|
features:
|
|
- A new configuration option
|
|
``[deploy]continue_if_disk_secure_erase_fails``, which
|
|
has a default value of False, has been added. If set to
|
|
True, the Ironic Python Agent will revert to a disk shred
|
|
operation if an ATA secure erase operation fails. Under
|
|
normal circumstances, the failure of an ATA secure erase
|
|
operation results in the node being put in ``clean failed``
|
|
state.
|
|
upgrades:
|
|
- A new configuration option
|
|
``[deploy]continue_if_disk_secure_erase_fails``, which
|
|
has a default value of False, has been added. The default
|
|
setting represents the standard behavior of the Ironic
|
|
Python Agent during a cleaning failure.
|