← Back to issue list

ValueError: '26.10' is not a valid BuilddBaseAlias on `ensure_guest_compatible()`

View original Github issue

Metadata

Project
craft-providers
Number
#979
Type
issue
State
closed
Author
tigarmo
Labels
Status: Triaged
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

Closed and triaged for internal tracking via Jira ticket CRAFT-5227. No explicit resolution or fix was documented in the provided context.

Suggested action:

No scores available.

Issue body

### Bug Description This issue is related to #969, but with a different constraint. The context here is using `build-base: devel` in Rockcraft. This is a 'supported' build-base value in the sense that we accept it on the project level, so it's weird that this would then raise an error that effectively means we actually can't use `build-base: devel`. Another argument is that `ensure_guest_compatible()` is only meant to check the very narrow case of focal host on plucky+ guest, so arguably it shouldn't fail on other configurations. ### To Reproduce A rockcraft project with: ```yaml base: base build-base: devel ``` ### part yaml ```shell ``` ### Relevant log output ```shell 2026-06-22 09:04:15.228 File "/snap/rockcraft/4543/lib/python3.12/site-packages/craft_application/commands/lifecycle.py", line 123, in _run_manager_for_build_plan 2026-06-22 09:04:15.228 provider.run_managed(build, bool(fetch_service_policy)) 2026-06-22 09:04:15.228 File "/snap/rockcraft/4543/lib/python3.12/site-packages/craft_application/services/provider.py", line 574, in run_managed 2026-06-22 09:04:15.228 with self.instance( 2026-06-22 09:04:15.228 File "/snap/rockcraft/current/usr/lib/python3.12/contextlib.py", line 137, in __enter__ 2026-06-22 09:04:15.228 return next(self.gen) 2026-06-22 09:04:15.228 ^^^^^^^^^^^^^^ 2026-06-22 09:04:15.228 File "/snap/rockcraft/4543/lib/python3.12/site-packages/craft_application/services/provider.py", line 263, in instance 2026-06-22 09:04:15.228 with provider.launched_environment( 2026-06-22 09:04:15.228 File "/snap/rockcraft/current/usr/lib/python3.12/contextlib.py", line 137, in __enter__ 2026-06-22 09:04:15.228 return next(self.gen) 2026-06-22 09:04:15.228 ^^^^^^^^^^^^^^ 2026-06-22 09:04:15.228 File "/snap/rockcraft/4543/lib/python3.12/site-packages/craft_providers/lxd/lxd_provider.py", line 242, in launched_environment 2026-06-22 09:04:15.228 bases.ensure_guest_compatible( 2026-06-22 09:04:15.228 File "/snap/rockcraft/4543/lib/python3.12/site-packages/craft_providers/bases/checks.py", line 115, in ensure_guest_compatible 2026-06-22 09:04:15.228 guest_base_alias = BuilddBaseAlias(guest_os_release.get("VERSION_ID")) 2026-06-22 09:04:15.228 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2026-06-22 09:04:15.228 File "/snap/rockcraft/current/usr/lib/python3.12/enum.py", line 757, in __call__ 2026-06-22 09:04:15.228 return cls.__new__(cls, value) 2026-06-22 09:04:15.228 ^^^^^^^^^^^^^^^^^^^^^^^ 2026-06-22 09:04:15.228 File "/snap/rockcraft/current/usr/lib/python3.12/enum.py", line 1171, in __new__ 2026-06-22 09:04:15.228 raise ve_exc 2026-06-22 09:04:15.228 ValueError: '26.10' is not a valid BuilddBaseAlias 2026-06-22 09:04:15.228 Full execution log: '/home/tiago.nobrega@canonical.com/.local/state/rockcraft/log/rockcraft-20260622-090034.957094.log' ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed and triaged for internal tracking via Jira ticket CRAFT-5227. No explicit resolution or fix was documented in the provided context.
qwen3.6-35b-a3b-mtp-q6
Staleness: 5
Complexity: 45
Confidence: 85
Support Request: 10
keep open Bug where ensure_guest_compatible() raises ValueError for '26.10' when using build-base: devel in Rockcraft. Currently triaged and tracked in Jira.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#2134450 snapcraft internal error: ValueError("'26.04' is not a valid BuilddBaseAlias") snapcraft (launchpad) closed Snapcraft raised a ValueError for invalid BuilddBaseAlias '26.04' during build. The issue was closed without comments or a patch, indicating abandonment or external resolution.
74%
#969 BuilddBaseAlias enum lookup raises bare ValueError — should raise a typed error craft-providers open Untriaged issue requesting BuilddBaseAlias enum lookup raise a typed CraftError instead of bare ValueError for better downstream error handling.
71%