build(deploy): provision Python 3.14 in Ansible + finish deploy-path sweep (#10872 Tier 2)#10875
Merged
Conversation
…n-version) + document OpenVINO 3.11 pin (#10872)
Contributor
✅ SSOT Configuration Compliance: Passing🎉 No hardcoded values detected that have SSOT config equivalents! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #10884.
Thinking Path
The Docker images run Python 3.14, but the Ansible deploy path (which provisions venvs directly on hosts via deadsnakes PPA) still provisioned and asserted python3.12. This finishes the migration for the non-container deploy path.
What Changed
Ansible provisioning (SLM + backend):
agent_config/defaults/main.yml,inventory/production.yml,group_vars/backend.yml:python_version3.12→3.14slm_manager/tasks/main.yml: venv version asserts 3.12→3.14 — fixes a real bug: the assert was pinned to '3.12' while the venv was already created withpython3.14 -m venv, so every deploy run needlessly tore down + rebuilt the venv and the health check never ran. Now idempotent.manifest.yml: deadsnakes runtime note → 3.14Deploy-path scripts / config:
.python-version(root +autobot-infrastructure/shared/config/) → 3.14shared/scripts/setup-runner-python.sh,install-bare-metal.sh: deadsnakes install/venv 3.12→3.14shared/scripts/cleanup-legacy-python.sh: keep-version safety gate 3.12→3.14 (the version it protects, not removes — leaving it at 3.12 would abort on a correctly-migrated host)autobot-infrastructure/autobot-backend/README.md: current-runtime prose → 3.14Intentionally NOT bumped (documented):
python3.11indeploy-native-services.yml+production.yml— pinned for OpenVINO (no 3.14 wheels). Added inline comments so future audits don't trip on it.Verification
yaml.safe_load_all;bash -nclean on all 3 scripts.Model Used
Opus 4.8
Part of #10872 (Tier 2). Follow-up doc-sweep for remaining 3.12 doc/test mentions to be filed separately.