upgrade from newton to ocata failed due to nova cell

Bug #1665011 reported by Jeffrey Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Critical
Jeffrey Zhang
Ocata
Fix Released
Critical
Jeffrey Zhang

Bug Description

when upgrading from newton to ocata branch, nova cell is required to be created before run db migration.

Changed in kolla-ansible:
assignee: nobody → Jeffrey Zhang (jeffrey4l)
Changed in kolla-ansible:
milestone: none → pike-1
importance: Undecided → Critical
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla-ansible (master)

Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/431508
Reason: This patch should not exist in master code.
moved into ocata branch https://review.openstack.org/#/c/435326/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/ocata)

Reviewed: https://review.openstack.org/435326
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=4265833cf8a31a38a54d43358d36221cf014da86
Submitter: Jenkins
Branch: stable/ocata

commit 4265833cf8a31a38a54d43358d36221cf014da86
Author: Jeffrey Zhang <email address hidden>
Date: Thu Feb 9 20:57:29 2017 +0800

    Map cell0 and sync None cell before nova database upgrade

    cell0 is required as of Ocata release in nova,
    before upgrade need to be created.
    By default in Newton cell0 is mapped to nova_api_cell0 database.
    To avoid future issues, first map cell0 to default database
    in Ocata nova_cell0, then discover and sync None cell.
    NOTE: None cell is where current instances are running.

    Tasks:
    * Map nova_cell0 before upgrade
    * Run simple_cell_setup to map and sync None cell
    * Follow common upgrade proceidure

    Co-Authored-By: Eduardo Gonzalez <email address hidden>
    Closes-Bug: #1665011
    Change-Id: Idcdff687df84dc11c7855187c25d7c240aae2d8e

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 4.0.0.0rc2

This issue was fixed in the openstack/kolla-ansible 4.0.0.0rc2 release candidate.

Changed in kolla-ansible:
status: Confirmed → Fix Released
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.