Skip to content

Does not track renamed events for projects backed by hashed storage

What does this MR do?

Does not track renamed events for projects backed by hashed storage on the primary node.

Are there points in the code the reviewer needs to double check?

Are other actions taken on the secondary in response to this event that are important?

Why was this MR needed?

Geo secondary receives a repository renamed event, and attempts gitlab_shell.mv_project(same_path, same_path) as a result. Fortunately, this will fail - the destination already exists, and gitlab-shell checks that - but I wonder if we can skip the move entirely.

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Closes #3508

Merge request reports