-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Build
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Problem
The v8.3-staging backport of SERVER-136184 added release distro enforcement, but four enterprise variants still select regular distros for crypt_create_lib. Waterfall builds fail before compilation.
ERROR: Release configuration(s) public-release-local, public-release: Evergreen release build requires a release-* distro; distro_id='amazon2-latest-large'. Assign the task or task group to a suitable release distro.
Affected variants
- enterprise-amazon2: amazon2-latest-large
- enterprise-amazon2-arm64: amazon2-arm64-latest-m8g-4xlarge
- enterprise-ubuntu2004-64: ubuntu2004-large
- enterprise-ubuntu2004-arm64: ubuntu2004-arm64-m8g-4xlarge
Fix
Assign crypt_create_lib explicitly to the corresponding release-* distro in the Amazon and Ubuntu release YAML, and exclude the task from the regular-host selectors. Extend evergreen/bazel_compile_test.py to check release crypt assignments across release variants and exercise the real compile wrapper in patch and waterfall modes.
Validation
- All 12 compile-wrapper tests pass after the fix.
- Evergreen validates the v8.3-staging project configuration.
- The regression test detects the missing assignments before the YAML fix.
- Audit of v9.0-staging found all 30 release crypt variants already assigned correctly.
This ticket and PR cover 8.3. The 8.0 changes will be handled in a separate PR.
- is related to
-
SERVER-136184 Require release Evergreen distros when the Bazel build wrapper uses release configurations
-
- Closed
-