ed74a062c1
Presently should the ATA erasure operation fails, IPA halts the cleaning process and the node goes to CLEANFAIL state as a result. This failure could be the result of a previous cleaning failure that left drive security enabled, for which code has been added in an attempt to address this case by attempting to unlock the the drive. In the event that an operator wishes to automatically fallback to disk scrubbing operations, the capability has been added through a driver_internal_info field "agent_continue_if_ata_erase_failed" that can be set to True, however defaults to False keeping the same behavior that IPA presently exhibits in the event of ATA erase operations failing. Partial-Bug: #1536695 Change-Id: I88edd9477f4f05aa55b2fe8efa4bbff1c5573bb1
15 lines
643 B
YAML
15 lines
643 B
YAML
---
|
|
features:
|
|
- The driver_internal_info internal setting
|
|
``agent_continue_if_ata_erase_failed`` allows operators
|
|
to enable disk cleaning operations to fallback from a failed
|
|
ata_erase operation to disk shredding operations.
|
|
fixes:
|
|
- IPA will now attempt to unlock a security locked drive
|
|
with a 'NULL' password if it is found to be enabled,
|
|
however this will only work if the password was previously
|
|
set to a 'NULL' value, such as if a failure during a previous
|
|
ata_erase sequence.
|
|
- Potential command failures in the secure erase process are
|
|
now captured and raised as BlockDeviceEraseError exceptions.
|