test: failing reproducer - no warning for default compatibility tag
Metadata
Current evaluation
Adds a failing test reproducing issue #454: BuilddBase without custom compatibility_tag emits no warning, causing LXD DNS conflicts. Proposes adding a logger.warning in __init__.
Suggested action: needs review
Reason: The PR adds a failing test for issue #454 (still open) and proposes a simple logger.warning fix in BuilddBase.__init__(). With 136 days of inactivity and 0 reviewer engagement, it needs maintainer attention to determine if the warning approach is acceptable or if a different solution is preferred.
Impact:
50
Quick Win:
40.0
Staleness:
75
Complexity:
20
Confidence:
65
Issue body
## 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
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
50
Quick Win:
40.0
Staleness:
75
Complexity:
20
Confidence:
65
|
needs review | Adds a failing test reproducing issue #454: BuilddBase without custom compatibility_tag emits no warning, causing LXD DNS conflicts. Proposes adding a logger.warning in __init__. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
60
Complexity:
10
Confidence:
85
|
needs review | Adds a failing test reproducing a LXD instance name conflict when BuilddBase lacks a custom compatibility_tag. Currently awaiting review with some CI checks failing. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
65
Complexity:
15
Confidence:
85
|
needs review | Adds a failing test and proposes a logger.warning fix in BuilddBase.__init__ to prevent LXD instance name collisions when compatibility_tag is omitted. Currently inactive for 79 days with no comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
60
Complexity:
15
Confidence:
85
|
needs review | Reproducer and fix for issue #454 where missing compatibility tags cause LXD instance name conflicts. Adds a failing test and suggests emitting a warning in BuilddBase.__init__(). Currently awaiting maintainer review with no comments or CI status. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-providers#454
(confidence 95%)
This PR is explicitly a reproducer for issue #454, which describes the same DNS conflict bug when default compatibility_tag is used.
Related issues
No related issues found above the similarity threshold.