You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we will read the node from database, and since it is
deleted, the id might be set to nil. Keep the node around and
just shutdown, so it is cleanly removed from notifier.
Fixesjuanfont#2118
Signed-off-by: Kristoffer Dalby <[email protected]>
Currently we will read the node from database, and since it is
deleted, the id might be set to nil. Keep the node around and
just shutdown, so it is cleanly removed from notifier.
Fixesjuanfont#2118
Signed-off-by: Kristoffer Dalby <[email protected]>
* add shutdown that asserts if headscale had panics
Signed-off-by: Kristoffer Dalby <[email protected]>
* add test case producing 2118 panic
Signed-off-by: Kristoffer Dalby <[email protected]>
* make stream shutdown if self-node has been removed
Currently we will read the node from database, and since it is
deleted, the id might be set to nil. Keep the node around and
just shutdown, so it is cleanly removed from notifier.
Fixesjuanfont#2118
Signed-off-by: Kristoffer Dalby <[email protected]>
---------
Signed-off-by: Kristoffer Dalby <[email protected]>
Is this a support request?
Is there an existing issue for this?
Current Behavior
A panic occurs when an online node is deleted:
Expected Behavior
The node should be removed and headscale should not crash.
Steps To Reproduce
headscale nodes list
shows the as "online"headscale nodes delete -i ID
Environment
Runtime environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: