Craft-application does not create unique LXD base instances
Metadata
Current evaluation
Closed with no linked PR or commit after more than three years of inactivity; the underlying optional compatibility-tag collision remained tracked in canonical/craft-providers#454.
Resolution: closed stale
Reason: Issue #139 was closed with no linked PR, commit, or maintainer explanation after 1,054 days of inactivity. Its underlying compatibility-tag problem remained open in canonical/craft-providers#454.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
Craft-application uses the same base instance name. LXD requires every instance to have a unique name, even if they are in different projects.
To make a unique name, the base instance name should include the name of app.
This was an easy error to produce because the `compatibility_tag` parameter is optional. See https://github.com/canonical/craft-providers/issues/454 for details.
### To Reproduce
Run 2 different craft-applications (i.e. charmcraft feature branch and rockcraft)
### part yaml
_No response_
### Relevant log output
```shell
Error: Failed start validation for device "eth0": Instance DNS name "base-instance-buildd-base-v3-craft-comub-523148486bd0c6cc722c" already used on network
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed with no linked PR or commit after more than three years of inactivity; the underlying optional compatibility-tag collision remained tracked in canonical/craft-providers#454. | |
| stealth/space-bunny-alpha | — | closed stale | Closed with no linked fix after prolonged inactivity; the underlying missing-compatibility-tag problem remains open in canonical/craft-providers#454. | |
| qwen/qwen3.6-35b-a3b | — | — | Craft-application generated non-unique LXD base instance names, causing project conflicts. Closed without resolution or linked fix, likely abandoned due to inactivity or upstream dependency. | |
| qwen/qwen3.6-35b-a3b | — | — | Report of non-unique LXD base instance names in craft-application was closed without resolution or linked pull requests. Zero comments and immediate closure indicate the bug report was abandoned and the defect remains unfixed. |
Update history
No update history recorded yet.
Related work
-
Blocked By:
canonical/craft-providers#454
(confidence 95%)
The reported name collision was caused by the optional compatibility tag discussed in that still-open issue.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #757 craft-providers leaves base lxd instance running on error | craft-providers | closed | Closed without a code fix after transfer from Charmcraft; tracking continued only in internal ticket CRAFT-4577, with no linked PR, commit, or maintainer explanation. | |
| #341 lxd: race condition when running multiple instances of craft-providers | craft-providers | closed | Fixed by merged PR #357, which rechecks LXC project existence after creation fails, preventing concurrent project-creation races (CRAFT-1849). |