tenant_id is still being used
Bug #1658479 reported by
Dima Kuznetsov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DragonFlow |
In Progress
|
Medium
|
Omer Anson | ||
Bug Description
Neutron put deprecation warning on using context.tenant_id, which will be removed sometime next cycle.
We should stop using it before tenant_id is removed and our master breaks.
/home/
| Changed in dragonflow: | |
| assignee: | nobody → Li Ma (nick-ma-z) |
| importance: | Undecided → Medium |
Revision history for this message
| Omer Anson (omer-anson) wrote | #1 |
| Changed in dragonflow: | |
| importance: | Medium → High |
| assignee: | Li Ma (nick-ma-z) → Omer Anson (omer-anson) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to dragonflow (master) | #2 |
| Changed in dragonflow: | |
| status: | New → In Progress |
| Changed in dragonflow: | |
| importance: | High → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on dragonflow (master) | #3 |
To post a comment you must log in.
Moved to high. I want to finish it before end of cycle, and it should be a simple search and replace fix.