no way for plugins to control upgrade order
Bug #1648176 reported by
YAMAMOTO Takashi
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grenade |
Triaged
|
Medium
|
Unassigned | ||
| networking-midonet |
New
|
Medium
|
Unassigned | ||
| networking-odl |
Triaged
|
Low
|
Unassigned | ||
Bug Description
there are no convenient ways for plugins to control upgrade order.
for example, a neutron plugin need to be upgraded before 05_neutron.
but currently in-tree plugins are always proceeded before grenade plugins.
it makes difficult to write a grenade plugin for neutron plugins cleanly.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix merged to networking-odl (master) | #1 |
| Changed in networking-midonet: | |
| importance: | Undecided → Medium |
| Changed in networking-odl: | |
| importance: | Undecided → Medium |
| Changed in networking-odl: | |
| importance: | Medium → Low |
| Changed in networking-odl: | |
| status: | New → Triaged |
| Changed in grenade: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit e99af3da7f90672
Author: Manjeet Singh Bhatia <email address hidden>
Date: Mon Dec 12 21:10:36 2016 +0000
Upgrade script for networking-odl
As updating neutron before networking-odl was ending up in failure
in db migrations because of stale networking-odl, this patch add a
logic to make sure it upgrades networking-odl before neutron so that
those db migrations happen smoothly. There are still 3 tests failing
from following scenarios.
1. tempest.
2. tempest.
Related-Bug: #1648176
Change-Id: I3d30375684cee3