starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Unique constraint failed on namespace name when registering clients using OIDC #333

New Issue
Closed
opened 2025-12-29 01:27:09 +01:00 by adam · 3 comments
adam commented 2025-12-29 01:27:09 +01:00
Owner
Copy Link

Originally created by @juanfont on GitHub (Sep 20, 2022).

When registering multiple clients at the same time using OIDC we might break the UNIQUE constraint on namespace name:

From oidc.go:

	namespace, err := h.GetNamespace(namespaceName)
	if errors.Is(err, ErrNamespaceNotFound) {
		namespace, err = h.CreateNamespace(namespaceName)

		if err != nil {
			log.Error().
				Err(err).
				Caller().
				Msgf("could not create new namespace '%s'", namespaceName)

I reckon this is a bit of a edge case in our integration tests, but seems to be there.

Originally created by @juanfont on GitHub (Sep 20, 2022). When registering multiple clients at the same time using OIDC we might break the UNIQUE constraint on namespace name: From `oidc.go`: ```go namespace, err := h.GetNamespace(namespaceName) if errors.Is(err, ErrNamespaceNotFound) { namespace, err = h.CreateNamespace(namespaceName) if err != nil { log.Error(). Err(err). Caller(). Msgf("could not create new namespace '%s'", namespaceName) ``` I reckon this is a bit of a edge case in our integration tests, but seems to be there.
adam added the stalebug labels 2025-12-29 01:27:09 +01:00
adam closed this issue 2025-12-29 01:27:09 +01:00
adam commented 2025-12-29 01:27:10 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Apr 19, 2023):

Is this still relevant with the new integration tests?

@kradalby commented on GitHub (Apr 19, 2023): Is this still relevant with the new integration tests?
adam commented 2025-12-29 01:27:10 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 17, 2023):

This issue is stale because it has been open for 180 days with no activity.

@github-actions[bot] commented on GitHub (Oct 17, 2023): This issue is stale because it has been open for 180 days with no activity.
adam commented 2025-12-29 01:27:11 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 1, 2023):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Nov 1, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#333
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?