liberty->mitaka upgrade completes, but neutron-openvswitch-agent unconfigured

Bug #1634923 reported by James Page on 2016-10-19
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack neutron-gateway charm
Medium
James Page
neutron-gateway (Juju Charms Collection)
Medium
James Page

Bug Description

Using the charm to upgrade from liberty->mitaka completes the package upgrade OK, but the upgrade process fails to take into account the switch in the ovs-agent from using ml2_conf.ini to openvswitch_agent.ini.

As a workaround, you can remove and re-add the relation between n-gateway and n-api; however the do_openstack_upgrade function should just dtrt.

James Page (james-page) wrote :

Login in resolve_configs:

    if plugin == OVS:
        # NOTE: deal with switch to ML2 plugin for >= icehouse
        drop_config = [NEUTRON_OVS_AGENT_CONF]
        if release >= 'mitaka':
            # ml2 -> ovs_agent
            drop_config = [NEUTRON_ML2_PLUGIN_CONF]

James Page (james-page) on 2017-01-05
Changed in neutron-gateway (Juju Charms Collection):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → James Page (james-page)
James Page (james-page) on 2017-02-23
Changed in charm-neutron-gateway:
assignee: nobody → James Page (james-page)
importance: Undecided → Medium
status: New → Triaged
Changed in neutron-gateway (Juju Charms Collection):
status: Triaged → Invalid
David Ames (thedac) on 2017-09-11
Changed in charm-neutron-gateway:
status: Triaged → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers