openstack/grenade
Code Issues Proposed changes

don't uninstall oslo.config

Browse Source 
There is a totally crazy sequencing issue that happens by uninstall
oslo.config here, don't do it. It's an incredibly old work around from
before we installed oslo.config as a non editable install.

Change-Id: Ic2364681e51e82e0d7b374728c177a47e04cbd1b
This commit is contained in:
Sean Dague 2014-12-02 16:04:11 -05:00
parent dfc2c87ed8
commit 010a882dad
1 changed files with 0 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
upgrade-oslo
View File

@ -27,13 +27,6 @@ source $TARGET_DEVSTACK_DIR/functions
source $TARGET_DEVSTACK_DIR/stackrc
source $TARGET_DEVSTACK_DIR/lib/oslo
# NOTE(sdague): in transitioning from grizzly to havana devstack we
# have an issue where we've pip installed an old oslo, but we are actually
# handing new oslo from the git tree instead. Due to the *fun* that is
# python library handling, this means if we don't uninstall old oslo, nova-manage
# will actually use the wrong one.
sudo pip uninstall -y oslo.config
# calls upgrade-oslo for specific release
upgrade_project oslo $GRENADE_DIR $BASE_DEVSTACK_BRANCH $TARGET_DEVSTACK_BRANCH