Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A network config keeps referring to a ghost, blank peer entry after it was removed from the peers list #3416

Open
nodakai opened this issue Mar 1, 2025 · 0 comments

Comments

@nodakai
Copy link

nodakai commented Mar 1, 2025

Describe the problem

To Reproduce

Steps to reproduce the behavior:

  1. Add peers X, Y to https://app.netbird.io/peers
  2. Define a network N with X and Y as its peering routers
  3. Remove peer X from https://app.netbird.io/peers
  4. Observe N still refers to a blank, ghost peer and Y

(2 peers might not be necessary)

Expected behavior

Either

  1. removing a peer which is a routing peer for an existing network should be blocked, or
  2. doing so should cascade to removing it from the routing peers lists for all existing networks

Are you using NetBird Cloud?

NetBird Cloud

NetBird version

0.37.1

NetBird status -dA output:

Do you face any (non-mobile) client issues?

Screenshots

Image

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant