This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
Fix vagrant provisioning failure by pinning pip python version #1262
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.
Overview
This approach was copied from another project.
The development VM has only Python 2.7 installed, and the default pip was recently upgraded to only work with Python 3. This pinning ensures that the VM provisions successfully.
Updates to the Ansible version and base box are not directly related, but we updated them as well to match a more recent, working project.
Connects #1265
Testing Instructions
$ vagrant destroy -f && ./scripts/setup
Checklist
fixup!
commits have been squashed