openstack command fails du to outdated python-*client

Bug #1407922 reported by Mathieu Rohon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
devstack
Invalid
Undecided
Unassigned

Bug Description

I'm running devstack on debian testing;

each "openstack" commands fails.

for instance I get this error :

+++ openstack user create admin --password mypwd --project --or-show -f value -c id
ERROR: openstackclient.shell Exception raised: (python-novaclient 2.20.1.dev32.g571dc98 (/opt/stack/python-novaclient), Requirement.parse('python-novaclient>=2.18.0'))

I also have this in my logs :

Found existing installation: python-novaclient 2.20.1.dev32.g571dc98
    Can't uninstall 'python-novaclient'. No files were found to uninstall.

Found existing installation: python-glanceclient 0.14.2.dev9.gcfe0623
    Can't uninstall 'python-glanceclient'. No files were found to uninstall.

Found existing installation: python-openstackclient 0.4.2.dev99.g2c9d263
    Can't uninstall 'python-openstackclient'. No files were found to uninstall.

Successfully installed python-glanceclient-0.14.2.dev9.gcfe0623 python-novaclient-2.20.1.dev32.g571dc98 python-openstackclient-0.4.2.dev99.g2c9d263

To workaround the issue I have to go to each /opt/stack/python-*client and run :

#git remote update && git pull origin master && sudo python setup.py develop

Revision history for this message
Dean Troyer (dtroyer) wrote :

This is working as designed. If you want the checked out repositories to be automatically updated ass RECLONE=yes to your local.conf. That will set each repo to a fresh clone of the specified branch (master by default) so if you have working changes make sure they are saved in another branch.

Changed in devstack:
status: New → Invalid
Revision history for this message
Mathieu Rohon (mathieu-rohon) wrote :

Thanks dean for your comment,

I know about the RECLONE option and I was using it. But in this case something wrong happened, and the "setup.py develop" didn't occur in the python-*client directory. I had to do it manually.

Revision history for this message
Mathieu Rohon (mathieu-rohon) wrote :

I'm facing the same issue while trying to use a bump on the requirements to fix a bug while trying to use latest tempest in devstack.

So I applied the patch which should result in updating tempest-lib to the version 0.1.0 :
https://review.openstack.org/#/c/148789/

then I ran devstack with stack.sh and the following error occured :

Found existing installation: tempest-lib 0.0.1
     Can't uninstall 'tempest-lib'. No files were found to uninstall.

then, pip freeze is telling me that tempest-lib 0.0.1 is still in use.

Those debian and ubuntu bugs seem related :
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1392288
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751827

Changed in devstack:
status: Invalid → New
Revision history for this message
Sean Dague (sdague) wrote :

This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.

Changed in devstack:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.