This issue happens, if we are trying to bring up devstack on a host, where there was a prior installation.
I see a related bug/discussion at [1], which might be helpful to track to get the right resolution to the issue.
Also, I worked-around the issue, by doing 'export PIP_UPGRADE=True' before running stack.sh, as suggested by[2]
This issue happens, if we are trying to bring up devstack on a host, where there was a prior installation.
I see a related bug/discussion at [1], which might be helpful to track to get the right resolution to the issue.
Also, I worked-around the issue, by doing 'export PIP_UPGRADE=True' before running stack.sh, as suggested by[2]
HTH,
suro
[1] - https:/ /bugs.launchpad .net/keystone/ +bug/1472503 /bugs.launchpad .net/devstack/ +bug/1468808/ comments/ 3
[2] - https:/