Skip to content

test: failing reproducer - no warning for default compatibility tag - #950

Draft
lengau wants to merge 1 commit into
mainfrom
fix/issue-454-default-compat-tag-collision
Draft

test: failing reproducer - no warning for default compatibility tag#950
lengau wants to merge 1 commit into
mainfrom
fix/issue-454-default-compat-tag-collision

Conversation

@lengau

@lengau lengau commented Apr 22, 2026

Copy link
Copy Markdown
Collaborator

Reproducer for #454

When two different applications create BuilddBase without a custom compatibility_tag, both receive the tag "buildd-base-v7". The resulting base LXD instance gets the same name in every project, and LXD refuses to start the second one with:

Error: Failed start validation for device "eth0":
Instance DNS name "base-instance-buildd-base-v3-..." already used on network

Failing test

test_default_compat_tag_logs_warning — shows that constructing BuilddBase without a custom compatibility_tag does not emit any warning.

Fix (quick)

In BuilddBase.__init__(), when compatibility_tag is None (default), emit a logger.warning telling the developer to pass a custom tag to avoid conflicts.

Closes #454

Adds a test verifying that BuilddBase logs a warning when no custom
compatibility_tag is provided.

Using the default tag causes all applications to share the same base
instance name, leading to LXD DNS name conflicts when multiple projects
use LXD simultaneously.

Quick fix per issue: log a warning so developers know to set a custom
compatibility_tag.

Fixes: #454

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using default compatibility tag can cause DNS name conflicts

1 participant