[GH-ISSUE #1568] Group is created twice, gets a "phantom peer" assigned and can't be deleted #2681

Open
opened 2026-08-05 00:48:24 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @b00nish on GitHub (Feb 12, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1568

Describe the problem

I tried to create a new Group during the creation of an Access Control Policy. The policy was supposed to have that same group as Source and Destination.
After doing so, I got not one but two new Groups (both with exactly the same name) under "Settings -> Groups".
Moreover both those Groups allegedly have a Peer assigned and therefore can't be deleted. Just that there is not one single Peer existing in that Netbird instance.
So I also can't get rid of the duplicated group because in order to do so I'd have to delete a "phantom peer" first, which I can't because there are 0 peers.

To Reproduce

I have not yet been able to reproduce the behaviour.
My (unproven) assumption is, that somehow by using the same group name in the Source and the Destination field I could trigger the creation of the same (or rather an identically named) group twice. Maybe because the creation of the "first" group (Source field) hasn't been finished when I entered the same name in the Destination field. But as I said: I couldn't reproduce it, so that's just a speculation.

Expected behavior

I expect not to have duplicate groups and phantom peers in my Netbird instance.

Are you using NetBird Cloud?

self-hosted

NetBird version

0.25.6

Screenshots

netbird1
Here you can see the same group twice, with each a peer assigned. (Don't mind the assigned setup-key, that one I added later but it had no influence on the situation.)

netbird2
Here you can see that there are no peers in that same instance. (In fact at the point where the duplicate groups were created, there never had been a peer in that freshly installed instance.)

Additional context

I'd love to know how to get rid of the duplicate groups.

Originally created by @b00nish on GitHub (Feb 12, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1568 **Describe the problem** I tried to create a new Group during the creation of an Access Control Policy. The policy was supposed to have that same group as Source and Destination. After doing so, I got not one but two new Groups (both with exactly the same name) under "Settings -> Groups". Moreover both those Groups allegedly have a Peer assigned and therefore can't be deleted. Just that there is not one single Peer existing in that Netbird instance. So I also can't get rid of the duplicated group because in order to do so I'd have to delete a "phantom peer" first, which I can't because there are 0 peers. **To Reproduce** I have not yet been able to reproduce the behaviour. My (unproven) assumption is, that somehow by using the same group name in the Source and the Destination field I could trigger the creation of the same (or rather an identically named) group twice. Maybe because the creation of the "first" group (Source field) hasn't been finished when I entered the same name in the Destination field. But as I said: I couldn't reproduce it, so that's just a speculation. **Expected behavior** I expect not to have duplicate groups and phantom peers in my Netbird instance. **Are you using NetBird Cloud?** self-hosted **NetBird version** 0.25.6 **Screenshots** ![netbird1](https://github.com/netbirdio/netbird/assets/12896406/65105baa-0efb-43d1-b5e8-816ca173400c) Here you can see the same group twice, with each a peer assigned. (Don't mind the assigned setup-key, that one I added later but it had no influence on the situation.) ![netbird2](https://github.com/netbirdio/netbird/assets/12896406/f6f8dfff-1910-4e3b-b738-3ca158d28243) Here you can see that there are no peers in that same instance. (In fact at the point where the duplicate groups were created, there never had been a peer in that freshly installed instance.) **Additional context** I'd love to know how to get rid of the duplicate groups.
saavagebueno added the bug label 2026-08-05 00:48:24 -04:00
Sign in to join this conversation.
No Label bug
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2681