ddohler
commented
3 years ago Can you try running vagrant box update and then destroy / reprovision? I wasn't able to reproduce the problem you're seeing, but then noticed that my vagrant box was from 2016, so I upgraded to the latest box version. That caused a different problem with package installation, for which I've pushed a fix. But the fact that different box versions can have different package installation behavior even with the same Ansible roles makes me wonder whether what you're seeing is related to the box version as well.
BryanQuigley
Overview
Due to an update to
get-pip.pyover the weekend, provisioning a fresh VM would fail when attempting to install pip. This fixes the issue.Testing Instructions
Bring up a fresh VM from scratch, confirm everything provisions successfully.
[ ] ~Is the CHANGELOG.md updated with any relevant additions, changes, fixes or removals following the format of keepachangelog?~ N/A: This didn't seem worth adding to the CHANGELOG.
[ ] ~Have you tested any front-end changes using the AoT build (
./scripts/update && ./scripts/server --nginx)?~ N/A: No frontend changes.I didn't write up an issue because by the time I got past this, I had fixed it.