Juno -> Kilo upgrade failed - Duplicate key name

Bug #1469621 reported by Ante Karamatić
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron-api (Juju Charms Collection)
Fix Released
High
James Page

Bug Description

I've done three Juno -> Kilo updates on three unrelated deployments (shared keystone thou), and in all three upgrades 2 out of 3 nodes (HA deployment) failed upgrading. Upgrade succeeded only on nodes that had VIP running. All other nodes failed. Running 'resolved --retry' resolved the issue on all of them.

Logs from one of the failed nodes is attached. All other nodes have same issue.

Tags: cpec

Related branches

Revision history for this message
Ante Karamatić (ivoks) wrote :
description: updated
Revision history for this message
James Page (james-page) wrote :

I see the issue:

    # set CONFIGS to load templates from new release
    configs.set_release(openstack_release=new_os_rel)
    # Before kilo it's nova-cloud-controllers job
    if new_os_rel >= 'kilo':
        stamp_neutron_database(cur_os_rel)
        migrate_neutron_database()

the neutron-api charm is making no effort to only sync from the leader.

Changed in neutron-api (Juju Charms Collection):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
James Page (james-page) wrote :

Running resolved --retry in turn on each unit will resolve this problem; alembic is clever enough to figure things out.

Fix proposed to ensure that db upgrade is only run on the lead unit.

Changed in neutron-api (Juju Charms Collection):
status: Confirmed → In Progress
assignee: nobody → James Page (james-page)
Revision history for this message
Ante Karamatić (ivoks) wrote :

I can confirm that lp:~james-page/charms/trusty/neutron-api/lp-1469621 branch does indeed solve the bug.

James Page (james-page)
Changed in neutron-api (Juju Charms Collection):
status: In Progress → Fix Committed
Revision history for this message
Felipe Reyes (freyes) wrote :

This fix is already available in /trunk[0] marking as Fix Released, and this landed in /next at July 3rd, before 15.07 was released, so setting 15.07 as milestone.

http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/neutron-api/trunk/view/head:/hooks/neutron_api_utils.py#L376

Changed in neutron-api (Juju Charms Collection):
milestone: none → 15.07
status: Fix Committed → 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.