Passing port's project_id in veth port bind
Bug #1649218 reported by
Dongcan Ye
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kuryr |
Fix Released
|
Undecided
|
Dongcan Ye | ||
Bug Description
Currently we passing port's tenant_id in veth binding driver when do port_bind.
This will wrong if the project id different with tenant id, also we need to keep consistent with _configure_
| Changed in kuryr: | |
| assignee: | nobody → Dongcan Ye (hellochosen) |
| Changed in kuryr: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to kuryr (master) | #1 |
| Changed in kuryr: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kuryr 0.3.0 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0cd6cfa02f388e3
Author: Dongcan Ye <email address hidden>
Date: Mon Dec 12 15:55:35 2016 +0800
Passing port's project_id in port_bind
Only get port's tenant_id if we're in Keystone v2.
Closes-Bug: #1649218
Change-Id: I7cf64183785f9e