Craft-application does not create unique LXD base instances
Metadata
Current evaluation
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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. craft-application generates non-unique LXD base instance names, causing conflicts. Fix requires including the application name in the instance identifier. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.