Deleting a node does not delete the associated route entry (v0.20.0) #438

Closed
opened 2025-12-29 01:29:19 +01:00 by adam · 5 comments
Owner

Originally created by @NetworkEngineer509 on GitHub (Feb 25, 2023).

Bug description
Deleting a node does not delete the associated route entry

To Reproduce

  1. Register a node with an advertised route
  2. Delete the node manually via headscale cli
  3. Check the routes, you will see the entry is still there, but the name is blank

Context info

  • Version of headscale used: v0.20.0

Here is the output of headscale route list showing the issue
image

Originally created by @NetworkEngineer509 on GitHub (Feb 25, 2023). <!-- Headscale is a multinational community across the globe. Our common language is English. Please consider raising the bug report in this language. --> **Bug description** Deleting a node does not delete the associated route entry <!-- A clear and concise description of what the bug is. Describe the expected bahavior and how it is currently different. If you are unsure if it is a bug, consider discussing it on our Discord server first. --> **To Reproduce** <!-- Steps to reproduce the behavior. --> 1. Register a node with an advertised route 2. Delete the node manually via headscale cli 3. Check the routes, you will see the entry is still there, but the name is blank **Context info** - Version of headscale used: v0.20.0 Here is the output of headscale route list showing the issue ![image](https://user-images.githubusercontent.com/34389163/221382751-9762b8a8-8a35-4d6a-ba26-f4774d01496b.png)
adam added the bug label 2025-12-29 01:29:19 +01:00
adam closed this issue 2025-12-29 01:29:19 +01:00
Author
Owner

@spomata commented on GitHub (Mar 2, 2023):

I had the same issue and ended up removing the route manually from the SQLite database (of course having closed headscale first).

@spomata commented on GitHub (Mar 2, 2023): I had the same issue and ended up removing the route manually from the SQLite database (of course having closed headscale first).
Author
Owner

@iFargle commented on GitHub (Mar 3, 2023):

Yep, seeing the same issue here.

@iFargle commented on GitHub (Mar 3, 2023): Yep, seeing the same issue here.
Author
Owner

@kradalby commented on GitHub (Mar 17, 2023):

Has anyone tried with @juanfont fix in #1244?

@kradalby commented on GitHub (Mar 17, 2023): Has anyone tried with @juanfont fix in #1244?
Author
Owner

@NetworkEngineer509 commented on GitHub (Mar 22, 2023):

Has anyone tried with @juanfont fix in #1244?

Yes, it's working now. I have deleted the old routes.

@NetworkEngineer509 commented on GitHub (Mar 22, 2023): > Has anyone tried with @juanfont fix in #1244? Yes, it's working now. I have deleted the old routes.
Author
Owner

@iFargle commented on GitHub (Mar 30, 2023):

Similar (potential) issue?
When an ephemeral machine falls off the network (as it should), the associated routes are left. Is this intended?

@iFargle commented on GitHub (Mar 30, 2023): Similar (potential) issue? When an ephemeral machine falls off the network (as it should), the associated routes are left. Is this intended?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#438