0f7b5a0896
When a hard error has occured with secure erase, we should attempt an unlock of the device becuase the current mode can prevent disk IO. This may upset some things like raid controllers even if they are in a pass-through mode. Change-Id: I32e1d962fbbb4a305d5dbebea92ac48ebd9b67ca Story: #2002546 Task: #22107
17 lines
706 B
YAML
17 lines
706 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes the ATA Secure Erase logic to attempt an immediate unlock in the
|
|
event of a failed attempt to Secure Erase. This is required to permit
|
|
fallback to make use of the ``shred`` disk utility.
|
|
|
|
In the event that an ATA Secure Erase operation fails during cleaning,
|
|
the disk will be write locked. In this case, the disk must be explicitly
|
|
unlocked.
|
|
|
|
This should also prevent failures where an ATA Secure Erase operation
|
|
fails with a pass-through disk controller, which may prevent the disk
|
|
from being available after a reboot operation. For additional information,
|
|
please see
|
|
`story 2002546 <https://storyboard.openstack.org/#!/story/2002546>`_.
|