Unable to upgrade using different repo and branch

Bug #1659317 reported by Lance Bragstad on 2017-01-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I would think this is more likely to be something developers hit instead of production deployments, but I figured I'd document it here.

I am using openstack-ansible to install a stable/newton deployment. After that, I have a clone of keystone that contains 3 patches that haven't merged yet [0]. I want to test the upgradeability of those patches since they specifically deal with database triggers. To have ansible install the bits that are not currently merged to master, I swapped the following two variables in /etc/openstack_deploy/user_variables.yml

keystone_git_repo: https://github.com/lbragstad/keystone
keystone_git_install_branch: add-domain-id-to-user-table

After that I run:

openstack-ansible playbooks/repo-build.yml

Which fails in [repo_build : Run venv process script] [1][2]. I am installing stable/newton by following a guide I wrote earlier in the release for performance testing upgrades from stable/newton to master [3].

I have attempted the above steps with `developer_mode=True` based on a suggestion from @cloudnull to get around requirements pinning.

[0] https://github.com/lbragstad/keystone/tree/add-domain-id-to-user-table
[1] http://cdn.pasteraw.com/bvv402meq7asd8lveqdor8au6zn9q2z
[2] http://cdn.pasteraw.com/5ko2ux9x9xkd6v5trsfcjv7n5ybi59r
[3] https://github.com/lbragstad/keystone-performance-upgrade#stable-newton-install-process

description: updated
Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Low

Hello Lance,

We discussed this during our bug triage today: http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2017-01-31.log.html#t2017-01-31T16:23:46

There is more attention that is required to fix this bug, so don't hesitate to tag someone along and make it work!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers