← Back to issue list

Managed instance names don't take the base into account

View original Github issue

Metadata

Project
craft-providers
Number
#544
Type
issue
State
open
Author
tigarmo
Labels
Type: Bug
Created
Updated
Closed
—

Current evaluation

Managed instances still do not persist and compare build-base, allowing a reused Ubuntu devel instance to bypass version validation; the triaged fix is to store it in InstanceConfiguration.

Suggested action: keep open

Reason: The maintainer-authored Type: Bug report is triaged: a maintainer reproduced it, investigation found that _ensure_os_compatible deliberately ignores VERSION_ID for devel bases, and the team selected storing build-base in InstanceConfiguration. Current code still has no build-base field and retains the devel early return, so the silent reuse problem remains valid and should stay open.

Evaluated by: mr-cal-bot

Impact: 52 Quick Win: 29 Complexity: 38 Confidence: 96 Actionability: 90

Issue body

### Bug Description The instance name currently reflects the app, project, build-on, build-for and inode of the directory, but not the project's base. What this means is that if a project's base changes (say, a Rockcraft's project `build-base` goes from `ubuntu@22.04` to `ubuntu@24.04` then the instance will be incorrectly reused with no warnings. Now granted this doesn't happen _too_ often, mostly to us when developing, but it's still a simple issue to fix. ### To Reproduce Create a project and change its effective base. ### part yaml _No response_ ### Relevant log output ```shell . ```

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 52
Quick Win: 29
Complexity: 38
Confidence: 96
Actionability: 90
keep open Managed instances still do not persist and compare build-base, allowing a reused Ubuntu devel instance to bypass version validation; the triaged fix is to store it in InstanceConfiguration.
stealth/space-bunny-alpha
Impact: 48
Quick Win: 23
Complexity: 45
Confidence: 93
Actionability: 88
keep open Managed instances can be silently reused after a project’s effective base changes. Maintainers agreed on metadata-based validation and later added platform separation; the bug remains open with no resolving PR linked.
qwen3.6-35b-a3b-mtp-q6
Impact: 60
Quick Win: 36
Staleness: 65
Complexity: 40
Confidence: 85
Support Request: 0
keep open Valid bug where managed instance names ignore the project base, causing incorrect reuse when bases change. Maintainers have identified the root cause and agreed on a fix.
qwen/qwen3.6-35b-a3b
Staleness: 15
Complexity: 45
Confidence: 95
Support Request: 5
keep open Managed instance names omit the project base, causing incorrect container reuse when bases change. Maintainers have triaged the bug, agreed on a solution involving instance config storage, and are actively discussing implementation details.
qwen3.6-35b-a3b-mtp-q6
Staleness: 45
Complexity: 60
Confidence: 90
Support Request: 5
keep open Bug where managed instance names exclude the project base, causing incorrect reuse. Maintainers have analyzed the issue, agreed on a fix involving instance config storage, and noted platform should also be considered. Still open.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-application#601 (confidence 99%)

    Merged PR adds the platform name to managed instance names, addressing the related platform collision but not missing build-base validation.

Related issues

No related issues found above the similarity threshold.