Skip to content

Fix the lock-yourself-out prevention code and spec for Geo

Nick Thomas requested to merge nick.thomas/gitlab-ee:cherry-pick-1eeaf62b into master

What does this MR do?

Geo is supposed to prevent you from adding the primary node to the database as a secondary. However, the validation implementing this was not running, and the spec was broken too.

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

Why was this MR needed?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Closes #3506 (closed)

Edited by Nick Thomas

Merge request reports