# Session Snapshot - 2026-04-21 ## Summary - Built a role-based deployment path for Proxmox VM provisioning and AI Tutor installation. - Added troubleshooting-driven improvements for Proxmox API auth handling. - Last test still failed due `401 Unauthorized` from `community.proxmox` modules, despite successful direct authenticated `curl` API check. - Session closed for the night with deployment still blocked in Ansible module auth path. ## Work Completed - Added/updated automation for: - Proxmox VM deployment role logic - Proxmox role defaults - Collection version baseline - Added optional Proxmox password-auth fallback in role tasks/defaults to unblock deployment path. ## Files Changed - ansible/requirements.yml - ansible/roles/proxmox_vm_deploy/defaults/main.yml - ansible/roles/proxmox_vm_deploy/tasks/main.yml ## Validation and Test Results - `ansible-inventory -i inventory/hosts.ini --list --ask-vault-pass`: - Passed after vault YAML fix. - Direct API auth check with token: - `GET /api2/json/cluster/resources?type=vm` returned HTTP 200. - Playbook execution: - `ansible-playbook -i inventory/hosts.ini playbooks/deploy-aitutor-vm.yml --ask-vault-pass` - Failed at `proxmox_vm_deploy : Gather current VMs on Proxmox node` with `401 Unauthorized`. ## New Technical Debt - None added in code comments (`@TODO` / `FIXME` not introduced this session). ## Open Issues - Ansible `community.proxmox` module auth path still fails with 401 while equivalent direct API call succeeds. - Environment contains multiple installed versions of `community.proxmox`; module resolution should be verified/standardized on target runner. ## Next Steps 1. Force/verify collection resolution to `community.proxmox 1.6.0` on watchtower runtime. 2. Re-test token auth via playbook. 3. If still blocked, use `proxmox_api_password` fallback for immediate deployment completion. 4. After unblock, revert to token-only auth and remove password fallback if desired. ## Session Notes - User requested to pack up for the night and commit all current changes.