[PR #2324] [CLOSED] client: Restart mgmt connection if networkMap serial is out of order #14985

Open
opened 2026-08-05 03:06:43 -04:00 by saavagebueno · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/netbirdio/netbird/pull/2324
Author: @mohamed-essam
Created: 7/25/2024
Status: Closed

Base: mainHead: main


📝 Commits (1)

  • 86f8045 client: Restart mgmt connection if networkMap serial is out of order

📊 Changes

1 file changed (+10 additions, -2 deletions)

View changed files

📝 client/internal/engine.go (+10 -2)

📄 Description

Describe your changes

Restart the connection to management service when serial received in networkMap is out of order. As well as adding a bit of logging around the serial check in networkMap updating client-side.

This is a workaround for the issue mentioned, the root cause is most likely a race condition in updating the networkMap serial in the management service itself, this PR will allow the issue to be non-apparent for users.

https://github.com/netbirdio/netbird/issues/2114

Checklist

  • Is it a bug fix
  • Is a typo/documentation fix
  • Is a feature enhancement
  • It is a refactor
  • Created tests that fail without the change (if possible)
  • Extended the README / documentation, if necessary

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbirdio/netbird/pull/2324 **Author:** [@mohamed-essam](https://github.com/mohamed-essam) **Created:** 7/25/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`86f8045`](https://github.com/netbirdio/netbird/commit/86f80451cf0486afa4c1b56a95ec51d360428d76) client: Restart mgmt connection if networkMap serial is out of order ### 📊 Changes **1 file changed** (+10 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `client/internal/engine.go` (+10 -2) </details> ### 📄 Description ## Describe your changes Restart the connection to management service when serial received in networkMap is out of order. As well as adding a bit of logging around the serial check in networkMap updating client-side. This is a workaround for the issue mentioned, the root cause is most likely a race condition in updating the networkMap serial in the management service itself, this PR will allow the issue to be non-apparent for users. ## Issue ticket number and link https://github.com/netbirdio/netbird/issues/2114 ### Checklist - [X] Is it a bug fix - [ ] Is a typo/documentation fix - [ ] Is a feature enhancement - [ ] It is a refactor - [ ] Created tests that fail without the change (if possible) - [ ] Extended the README / documentation, if necessary --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2026-08-05 03:06:43 -04:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#14985