VIM registry should not use keystone information from tacker.conf
Bug #1603851 reported by
yong sheng gong
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-tackerclient |
Fix Released
|
Medium
|
yong sheng gong | ||
| tacker |
Fix Released
|
Medium
|
Sripriya | ||
Bug Description
Problem:
when we found the auth in VIM registry is v3, we are using the domain information from tacker keystone configuration. In fact, these keystone probably are different.
solution:
add domain information in vim registry information and use them if the auth is V3.
| Changed in tacker: | |
| assignee: | nobody → yong sheng gong (gongysh) |
| Changed in python-tackerclient: | |
| assignee: | nobody → yong sheng gong (gongysh) |
| Changed in python-tackerclient: | |
| importance: | Undecided → Medium |
| Changed in tacker: | |
| importance: | Undecided → Medium |
| Changed in tacker: | |
| assignee: | yong sheng gong (gongysh) → Sripriya (sseetha) |
| Changed in tacker: | |
| assignee: | Sripriya (sseetha) → yong sheng gong (gongysh) |
| Changed in tacker: | |
| assignee: | yong sheng gong (gongysh) → Sripriya (sseetha) |
| Changed in python-tackerclient: | |
| status: | In Progress → Fix Committed |
| Changed in tacker: | |
| status: | In Progress → Fix Committed |
| Changed in tacker: | |
| status: | Fix Committed → Fix Released |
| Changed in python-tackerclient: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/343439
Review: https:/