Have we resolved this? What is the long term strategy on this?
On Mon, Jul 20, 2015 at 10:51 PM Andrew Woodward awoodw...@mirantis.com
wrote:
I found this after noon that fuel-web CI was broken due to the recent
release of oslo.config and oslo.utils 2.0.0 [1]
I attempted to muck around with
I found this after noon that fuel-web CI was broken due to the recent
release of oslo.config and oslo.utils 2.0.0 [1]
I attempted to muck around with the pinning of the requirements.txt and had
initial success with it [2] but later found that it's failing the
test_check_requirements_conflicts