cinder latest requirements breaking things, must be a string

[Victor Laza]

The below trace brings into my attention: https://github.com/openstack/cinder/commit/238df8b82e8d078279f98d90cf9bcfd39dd7cbc8
and more specific:

requirements.txt
+enum34;python_version=='2.7' or python_version=='2.6'

that breaks things

04:45:35 error in setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Expected version spec in enum34;python_version=='2.7' or python_version=='2.6' at ;python_version=='2.7' or python_version=='2.6'
04:45:35 ExecRetry : System.Management.Automation.RuntimeException: Failed to install
04:45:35 cinder from repo
04:45:35 At C:\cinder-ci\windows\scripts\create-environment.ps1:147 char:1
04:45:35 + ExecRetry {
04:45:35 + ~~~~~~~~~~~
04:45:35 + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
04:45:35 tion
04:45:35 + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
04:45:35 n,ExecRetry

[Victor Laza (vlaza)]

Seems also related to pbr==1.3.0 as with 1.2.0 builds were passing

[Victor Laza (vlaza)]

Seems that capping pbr to 1.2.0 on Windows fixes the problem for now; we will investigate further why latest pbr breaks things on Windows.

[Amey Bhide (abhide)]

Seems like devstack is downgrading pbr

Might be related to: https://bugs.launchpad.net/devstack/+bug/1468808

[Amey Bhide (abhide)]

Adding PIP_UPGRADE=True to localrc in devstack; seems to solve this problem for now