Changing the network view name causes sync issues
Bug #1541073 reported by
John Belamaric
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-infoblox |
Fix Released
|
Medium
|
Hosung Hwang | ||
| 2.0 |
Fix Released
|
Medium
|
Hosung Hwang | ||
Bug Description
When using the "Tenant" network view mapping scope, new network views are created for each tenant, with the name:
<tenant_
This is painful to look at. If you change it, it gets recreated with the next subnet creation, causing sync issues.
While it is possible to pre-create the network view and tag it with the tenant name (and thus have a different named network view), that direction takes more planning.
Instead, we should be able to change the Network View name after it is created, and the connection to the tenant should not be lost.
| Changed in networking-infoblox: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Hosung Hwang (hhwang-2) |
| Changed in networking-infoblox: | |
| status: | New → Confirmed |
Revision history for this message
| Hosung Hwang (hhwang-2) wrote | #1 |
To post a comment you must log in.
https:/