Skip to content

Geo - Update the `geo:set_secondary_as_primary` rake task to do nothing on a Geo primary site

What does this MR do and why?

This MR changes the geo:set_secondary_as_primary rake task to not update the Geo node on a Geo primary site. This change allows admins to run this task a couple of additional times with no side effects and fix #335924 (comment 704216643).

How to set up and validate locally

  1. Run the following command on a Geo primary or a recently promoted node multiple times:
    gitlab-rake geo:set_secondary_as_primary
  2. The rake task should not output errors.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports