Bypass ongoing imports in the Guard worker
Proposal
This issue originates from #351337 (comment 837857367).
The GuardWorker for the container registry phase 2 migration currently aborts all imports that have exceeded the container_registry_import_max_step_duration
.
In these cases, we want to keep the container repositories in the importing
or pre_importing
migration_state
s.
We should:
- Update the Guard worker to request the true status from the registry and skip aborting the import if the status is
pre_import_in_progress
orimport_in_progress
. - Log when (1.) occurs so we can detect stale imports via Kibana