Using default compatibility tag can cause DNS name conflicts
Metadata
Current evaluation
Missing compatibility tags still produce identical LXD base-instance names across projects, causing DNS conflicts and failed launches; the proposed warning and API redesign remain unimplemented.
Suggested action: keep open
Reason: The issue has a maintainer-filed Type: Bug label, an exact two-project reproducer, and a concrete DNS collision error. Current code still accepts compatibility_tag=None, only overrides BuilddBase's default when a tag is supplied, and derives the LXD base name from that tag, so the failure remains valid; the warning is easy, while the required-tag redesign involves major-release compatibility work.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
56
Quick Win:
28
Complexity:
43
Confidence:
96
Actionability:
89
|
keep open | Missing compatibility tags still produce identical LXD base-instance names across projects, causing DNS conflicts and failed launches; the proposed warning and API redesign remain unimplemented. | |
| stealth/space-bunny-alpha |
Impact:
55
Quick Win:
28
Complexity:
45
Confidence:
97
Actionability:
92
|
keep open | Missing compatibility tags give different projects identical LXD base instance names, causing DNS conflicts and failed launches. A warning is proposed for now; a required-tag API change is deferred to a major release. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
50
Quick Win:
35
Staleness:
75
Complexity:
30
Confidence:
60
Support Request:
10
|
needs triage | Bug: missing compatibility_tag causes LXD DNS name conflicts when launching instances for multiple projects. Open for ~3 years with no maintainer comments or assignee. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
20
Confidence:
80
Support Request:
5
|
close stale | Bug report detailing DNS name conflicts in LXD when craft-providers launches instances without a compatibility tag. Includes reproduction steps and proposed warning/long-term fix. Unaddressed for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
65
Complexity:
20
Confidence:
85
Support Request:
0
|
keep open | Bug where omitting the compatibility_tag in craft-providers causes LXD instance DNS name collisions. Includes reproduction steps and proposed warning/fix. Currently open with no maintainer follow-up. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-application#139
(confidence 98%)
The issue explicitly identifies craft-application#139 as the source of the collision.
Related issues
No related issues found above the similarity threshold.