Bug #207
Virtual Networks shouldn't be overwritten if a new with same name is created
| Status: | Closed | Start date: | 03/23/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 100% | |
| Category: | Core & System | |||
| Target version: | Release 2.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: |
Description
Uniqueness should be define by ID, NAME, USER; and not by ID and NAME as it is now
Associated revisions
Little change in style in role datatable (#207)
History
#1
Updated by Frank Stutz about 11 years ago
On this topic / bug it should be possible to update a vn pool without it being recreated as you loose your vid assignments.
#2
Updated by Tino Vázquez about 11 years ago
- % Done changed from 0 to 100
- Resolution set to fixed
This has been tackled in branch-206, now merged in master since e86c0f07ebc9d08bfcc4cfc0d334b78bbb4fb88b.
Now the behavior dictates that a new network allocation with the same name as a previously existing one will fail.
#3
Updated by Ruben S. Montero about 11 years ago
- Status changed from New to Closed