neutron migrations broken when neutron-lbaas installed

Bug #1511756 reported by Matt Thompson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
High
Matt Thompson
Liberty
Fix Released
High
Matt Thompson
Trunk
Fix Released
High
Matt Thompson

Bug Description

The neutron_migrations_facts module gets confused when neutron-lbaas is installed as it introduces an extra set of migrations.

Matt Thompson (mattt416)
Changed in openstack-ansible:
assignee: nobody → Matt Thompson (mattt416)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (master)

Fix proposed to branch: master
Review: https://review.openstack.org/240560

Changed in openstack-ansible:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (liberty)

Fix proposed to branch: liberty
Review: https://review.openstack.org/241176

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

Change abandoned by Matt Thompson (<email address hidden>) on branch: liberty
Review: https://review.openstack.org/241176
Reason: This change was applied to master, going to abandon and backport the change in master.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (master)

Reviewed: https://review.openstack.org/240560
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=edd50471d9807d64504f7f04496f23bbbafbb221
Submitter: Jenkins
Branch: master

commit edd50471d9807d64504f7f04496f23bbbafbb221
Author: Matt Thompson <email address hidden>
Date: Thu Nov 12 14:20:54 2015 +0000

    Update neutron_migrations_facts

    This change does the following to neutron_migrations_facts:

    - updates MIGRATIONS dict by adding entries for each neutron
      sub-project while also adding keys to track which sub-projects are
      installed and which migrations need to be run (contract or expand)
    - takes subproject migrations into account (neutron-lbaas as an
      example)
    - updates neutron_venv_lib_dir and neutron_non_venv_lib_dir by removing
      reference to neutron specifically since these vars need to be used
      for all neutron subprojects also

    We also update neutron_db_setup.yml to use MIGRATIONS['run_contract']
    and MIGRATIONS['run_expand'] to determine if neutron or a subproject
    has migrations which need to be applied.

    Closes-Bug: #1511756
    Change-Id: I3a385f4530620718ba01a7b5e993ba08ce38f7c7

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (liberty)

Reviewed: https://review.openstack.org/241176
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=aa9230b5a5cdf0e7baf57b5fb8fc6e149912b0fa
Submitter: Jenkins
Branch: liberty

commit aa9230b5a5cdf0e7baf57b5fb8fc6e149912b0fa
Author: Matt Thompson <email address hidden>
Date: Thu Nov 12 14:20:54 2015 +0000

    Update neutron_migrations_facts

    This change does the following to neutron_migrations_facts:

    - updates MIGRATIONS dict by adding entries for each neutron
      sub-project while also adding keys to track which sub-projects are
      installed and which migrations need to be run (contract or expand)
    - takes subproject migrations into account (neutron-lbaas as an
      example)
    - updates neutron_venv_lib_dir and neutron_non_venv_lib_dir by removing
      reference to neutron specifically since these vars need to be used
      for all neutron subprojects also

    We also update neutron_db_setup.yml to use MIGRATIONS['run_contract']
    and MIGRATIONS['run_expand'] to determine if neutron or a subproject
    has migrations which need to be applied.

    This cherry-pick has a small edit to change 'mitaka' to 'liberty' in
    playbooks/roles/os_neutron/tasks/neutron_db_setup.yml in order to
    apply the series name appropriately.

    Closes-Bug: #1511756
    Change-Id: I3a385f4530620718ba01a7b5e993ba08ce38f7c7
    (cherry picked from commit edd50471d9807d64504f7f04496f23bbbafbb221)

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 12.0.8

This issue was fixed in the openstack/openstack-ansible 12.0.8 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 12.0.9

This issue was fixed in the openstack/openstack-ansible 12.0.9 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 13.0.0

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 12.0.11

This issue was fixed in the openstack/openstack-ansible 12.0.11 release.

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.