Routes version 2.3 broke the way we register routes
Bug #1563028 reported by
Amrith Kumar
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Critical
|
Amrith Kumar | ||
neutron |
Fix Released
|
High
|
Cedric Brandily | ||
Kilo |
New
|
Undecided
|
Unassigned |
Bug Description
Routes v2.3 which just came out included this change
https:/
which changed submap.connect() in a way that broke the way Trove registers routes.
We now need to provide a routename and a path as independent arguments.
I tried to make sense of the documentation at http://
This will likely need to go to stable/mitaka as well.
Changed in neutron: | |
assignee: | nobody → Cedric Brandily (cbrandily) |
tags: | added: liberty-backport-potential mitaka-backport-potential |
tags: | added: kilo-backport-potential |
tags: | removed: kilo-backport-potential liberty-backport-potential mitaka-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/298419
Review: https:/