openstack-ansible

Neutron requires a new sha in order to upgrade from Icehouse to Juno

Bug #1412597 reported by Kevin Carter
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack-ansible
Invalid
Undecided
Matt Thompson
Juno
Fix Released
High
Matt Thompson
openstack-ansible 10.1.2
Trunk
Invalid
Undecided
Matt Thompson

Bug Description

When upgrading from 9.0.x to 10.1.x neutron breaks with an error reporting a broken foreign key. This issue is resolved in "2014.2.1" and confirmed by this related bug: https://bugs.launchpad.net/neutron/+bug/1397796

Being that the neutron version discrepancy prohibits upgrades from Icehouse it will need to make it into the next release as it impacts the stability and supportability of all projects. This also brings to light that the present release of Juno from `openstack-ansible` does not run on the current upstream "stable" code. Whle we need to upgrade the release version for neutron we should also look at the rest of our supported projects too.

See original description
Kevin Carter (kevin-carter)
no longer affects: openstack-ansible/icehouse
no longer affects: openstack-ansible/juno
description: updated
Darren Birkett (darren-birkett)
tags: added: juno-backport-potential
Revision history for this message
Matt Thompson (mattt416) wrote :

Tried deploying 2014.2.1 across the board and it worked fine, with exception of horizon. Installation of horizon failed as requirements.txt is looking for "xstatic-jasmine>=1.3.1.1,<2", but this cannot be satisfied using http://mirror.rackspace.com/rackspaceprivatecloud/python_packages/juno/.

I tried running a tempest smoke test against this environment and only got a few swift-related failures which I'm still trying to figure out (even on master).

--Matt

Revision history for this message
Jacob Wagner (swagner1104) wrote :

Saw this on a greenfiled deployment today. Will update with more info, trying to replicate.

Revision history for this message
Jacob Wagner (swagner1104) wrote :

Verified:

Branch: Juno
Install: Greenfield

I am seeing this db migrate missing key issue on a greenfield install of the juno branch

http://jenkins.propter.net/view/QE/job/qe-build-sat6-lab02/16/console

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (juno)

Fix proposed to branch: juno
Review: https://review.openstack.org/150151

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on os-ansible-deployment (juno)

Change abandoned by Kevin Carter (<email address hidden>) on branch: juno
Review: https://review.openstack.org/150151
Reason: duplicate. abandoned in favor of "https://review.openstack.org/#/c/150143/"

Jesse Pretorius (jesse-pretorius)
Changed in openstack-ansible:
milestone: 10.1.2 → none
status: Triaged → In Progress
assignee: Kevin Carter (kevin-carter) → Matt Thompson (mattt416)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (juno)

Reviewed: https://review.openstack.org/150143
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=c31df5240e5ec871d90987842e80649ea94273b6
Submitter: Jenkins
Branch: juno

commit c31df5240e5ec871d90987842e80649ea94273b6
Author: Matt Thompson <email address hidden>
Date: Mon Jan 26 15:34:14 2015 +0000

    Bump OpenStack versions to 2014.2.1

    We are currently hitting a neutron bug
    (https://bugs.launchpad.net/neutron/+bug/1397796) which is preventing a
    neutron-db-manage from completing when running git_install_branch
    2014.2. This change bumps OpenStack versions to 2014.2.1 where the
    issue is resolved. We also bump rpc_release to 10.1.2rc1 to point to a
    wheel repo which has necessary wheels for bump to 2014.2.1.

    Closes-Bug: #1412597
    Change-Id: If0285847dc7361b66f86ff77b705a6a415f58915

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

Other bug subscribers

Remote bug watches

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