You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(ansible): site.yml backend play unrunnable — references nonexistent roles and a dangling backend.env.j2 template #10048
The Deploy Backend Services play in autobot-slm-backend/ansible/site.yml:53-59 cannot run:
Nonexistent roles — the play lists python and fastapi_app; neither exists under ansible/roles/ (there is python312, no fastapi_app). Ansible fails at role resolution before any task executes.
Dangling template — roles/backend_services/tasks/main.yml task "Generate environment configuration" uses src: backend.env.j2, but the role has no templates/ dir and no playbook-adjacent copy exists; the only backend.env.j2 lives in roles/backend/templates/ which is outside this role's template search path. The task would fail with "could not find or access".
The role also duplicates the backend deploy with a divergent layout (/opt/autobot/app + /opt/autobot/venv vs the backend role's /opt/autobot/autobot-backend with in-tree venv) and syncs {{ playbook_dir }}/../ (the SLM backend tree) as the app code.
#10005 already redirected the role's systemd-unit task to the canonical roles/backend/templates/autobot-backend.service.j2, so the unit file is no longer a second source of truth. Remaining decision: either wire backend_services properly (fix role list, env template, venv layout) or retire the play in favour of the maintained roles/backend path used by the wizard playbooks.
Activity
fix(ansible): per-user tmp paths, site.yml roles, backend_port 8001 (#…