Skip to content

Raise the error when repository storage move fails

James Fargher requested to merge raise_error_when_repository_move_fails into master

What does this MR do?

This is a partial solution to #333277 (closed)

Right now when repository storage moves fail, the only way to tell is to check the state column in the database, then try and correlate that to logs for the specific repository to see what failed. This makes it very difficult to debug especially since the sidekiq job is considered successful. Instead we should explode and let sidekiq error reporting tell the user that the move failed.

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by James Fargher

Merge request reports