92eefc9d63
The tl;dr is that we changed ``inspecting`` to include a ``inspect wait`` state. Unfortunately we never spotted the logic inside of the db API. We never spotted it because our testing in inspection code uses a mocked task manager... and we *really* don't have intense db testing because we expect the objects and higher level interactions to validate the lowest db level. Unfortunately, because of the out of band inspection workflow, we have to cover both cases in terms of what the starting state and ending state could be, but we've added tests to validate this is handled as we expect. Change-Id: Icccbc6d65531e460c55555e021bf81d362f5fc8b
6 lines
143 B
YAML
6 lines
143 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes a database API internal check to update the
|
|
``inspection_finished_at`` field upon the completion of inspection.
|