We are seeing this in stable/kilo as well, and I believe I know the problem.
First, we isolate each service into its own virtualenv, so the only requirements that will come in are those of the project itself (nova).
Nova requires python-glanceclient, which in turn requires requests, and this requirement is uncapped. The requests library had a new release recently, http://docs.python-requests.org/en/latest/community/updates/#id1 , which bundles urllib3 1.12. Now python-glanceclient is trying to use this new requests and urllib3 and it has a bad time. I was able to resolve this simply by downgrading the requests library to 2.7.0, which was the previous release.
I believe that global-requirements for stable/kilo should cap requests to <=2.7.0 and after that's done, python-glanceclient should also be capped.
Meanwhile we can downgrade requests in our virtualenv as part of the deployment and not be blocked by this bug any longer.
We are seeing this in stable/kilo as well, and I believe I know the problem.
First, we isolate each service into its own virtualenv, so the only requirements that will come in are those of the project itself (nova).
Nova requires python- glanceclient, which in turn requires requests, and this requirement is uncapped. The requests library had a new release recently, http:// docs.python- requests. org/en/ latest/ community/ updates/ #id1 , which bundles urllib3 1.12. Now python-glanceclient is trying to use this new requests and urllib3 and it has a bad time. I was able to resolve this simply by downgrading the requests library to 2.7.0, which was the previous release.
I believe that global-requirements for stable/kilo should cap requests to <=2.7.0 and after that's done, python-glanceclient should also be capped.
Meanwhile we can downgrade requests in our virtualenv as part of the deployment and not be blocked by this bug any longer.