fix(ProviderService): set base compatibilty tag
Metadata
Current evaluation
Merged PR #142 via commit 7df5e8a3, setting an application-specific ProviderService compatibility tag to fix #139 and work around craft-providers#454.
Resolution: closed resolved
Reason: PR #142 was merged into main as commit 7df5e8a3. Its two-line change fixes the missing unique base compatibility tag that prevented LXD instances from launching correctly.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the guidelines for contributing?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox`?
-----
Set the base compatibility tag so that is it unique per each application.
This works around a bug in craft-providers where LXD instances will fail to launch. It is described in detail here: https://github.com/canonical/craft-providers/issues/454
Fixes #139
(CRAFT-2230)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #142 via commit 7df5e8a3, setting an application-specific ProviderService compatibility tag to fix #139 and work around craft-providers#454. | |
| stealth/space-bunny-alpha | — | closed resolved | PR #142 by mr-cal merged as commit 7df5e8a3, setting a per-application base compatibility tag in ProviderService as a workaround for craft-providers#454 (LXD DNS name conflicts). Closes craft-application#139. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #142 made ProviderService compatibility tags application-specific, working around the LXD launch failure in craft-providers#454 and fixing #139 (CRAFT-2230). | |
| qwen/qwen3.6-35b-a3b | — | — | Merged a fix setting a unique base compatibility tag per application, resolving craft-providers LXD launch failures and closing issue #139. Approved by two reviewers and passed CI. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-application#139
(confidence 100%)
PR #142 explicitly states that it fixes the unique LXD base-instance issue reported in #139.
-
Related To:
canonical/craft-providers#454
(confidence 99%)
The PR works around the compatibility-tag collision and LXD launch failure documented in craft-providers#454.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #865 fix(provider): bump compatibility tag | craft-application | merged | Merged PR #865 as commit 20757ad2, bumping Provider's compatibility tag to prevent reuse of instances created before the State service. | |
| #105 Custom compatibility tags in the provider service | craft-application | open | Feature request: add a per-application integer addendum (e.g. in AppMetadata, default 0) to the provider base compatibility_tag so charmcraft needn't override ProviderService/get_base. Open, unlabelled, tracked as CRAFT-2606. |