Copying over from #1352:
- Detect when a dataset is affected by a terminal or sustained retention/proving condition that can lead to termination.
- Move the dataset into an explicit review required state.
- Record the reason, first detection time, current state, and review deadline.
- Activate a persistent operator alert through the alert manager.
Resolve the alert and cancel pending termination if the underlying condition recovers.- Preserve enough failure and service context for the SP to investigate the condition, including through external systems such as the MSP.
- Maintain an audit trail of state transitions and operator actions.
After recent work our pending termination marking should only be happening if errors are truly unrecoverable so I've crossed out point 5.
PR #1332 probably handles point 4 as well, though I'll let @LexLuthr comment on this since he opened the originating issue after filing that PR.
Overall I am imagining a UI page which immediately presents operator with the biggest dataset problems and information on the nature of the problems. Since I haven't been running the latest UI its possible that this is mostly covered by the latest UI improvements cc @snadrus.
Copying over from #1352:
Resolve the alert and cancel pending termination if the underlying condition recovers.After recent work our pending termination marking should only be happening if errors are truly unrecoverable so I've crossed out point 5.
PR #1332 probably handles point 4 as well, though I'll let @LexLuthr comment on this since he opened the originating issue after filing that PR.
Overall I am imagining a UI page which immediately presents operator with the biggest dataset problems and information on the nature of the problems. Since I haven't been running the latest UI its possible that this is mostly covered by the latest UI improvements cc @snadrus.