missing alembic migrations due to use of git based workflows
Bug #1627656 reported by
James Page
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-l2gw |
Fix Released
|
Undecided
|
Unassigned | ||
networking-odl |
Fix Released
|
Undecided
|
Unassigned | ||
networking-sfc |
Fix Released
|
Undecided
|
Unassigned | ||
tap-as-a-service |
Fix Released
|
Undecided
|
Unassigned | ||
networking-l2gw (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
New
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Unassigned | ||
networking-odl (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Triaged
|
High
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Unassigned | ||
neutron-taas (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Unassigned |
Bug Description
Various openstack related packages are missing required neutron database migrations due to the direct use of a git based workflow of merging upstream tags and generating orig.tar.xz directly from the git tree for packaging. This is *not* the same process as generated a sdist tarball, and as a result, files that need to reside in the python module get missed - this includes alembic migrations.
Known impacts:
networking-odl
vmware-nsx (bug 1574610)
A simple fix is to switch to using the upstream published release artefacts, rather than directly using git.
Changed in neutron-taas (Ubuntu Xenial): | |
status: | New → Invalid |
Changed in networking-l2gw (Ubuntu Yakkety): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in neutron-taas (Ubuntu Yakkety): | |
importance: | Undecided → High |
status: | New → Triaged |
To post a comment you must log in.
Note that this does not impact the core neutron* packages, as these don't use the same git based workflow as Debian does, relying on git-buildpackage, upstream release artefacts and pristine-tar instead.