Use rally-openstack's upper constraints #18
Merged
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.
docker-rally images built at present without upper constraints fail at the end of a rally/tempest verification with the following errors:
It's unclear what is causing the problem, but rebuilding the image with dependencies pinned to the last known working image (the 1.4-dev tag) results in a working image.
Looking at the rally-openstack source, the project maintains its own upper constraints file that it uses in testing. It makes sense for us to also use this to aim for a consistent and tested set of dependencies.
This change also adds Docker build args for the rally-openstack repo, version and upper constraints.