Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,331
    • Merge requests 1,331
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #338231
Closed
Open
Issue created Aug 11, 2021 by Zack Cuddy@zcuddy🔴Maintainer

Geo 2.0 Regression - Removing Primary Nodes in the UI

What/Why

In Geo, you should be able to remove the Primary Node if there are no other secondary nodes. However, this was lost during our redesign and this button is disabled always on a Primary node.

The documentation further states that you should be able to remove a Primary Geo Node. However, it fails to mention the section above it that you must first remove all secondary nodes: https://docs.gitlab.com/ee/administration/geo/replication/disable_geo.html#remove-the-primary-site-from-the-ui.

Proposal

Fix the regression to allow for Geo Nodes to be removed when no secondary nodes exist.
Update documentation to be clear that all secondary nodes must first be removed.

Workaround

Delete the node via the Geo Nodes API

Assignee
Assign to
Time tracking