I create a vim twice with same config-file and same name, find it successed.
yanxa@ubuntu:~/mywork$ tacker vim-register --config-file vim-yanxingan2.yaml vim-yanxa2
yanxa@ubuntu:~/mywork$ tacker vim-register --config-file vim-yanxingan2.yaml vim-yanxa2
yanxa@ubuntu:~/mywork$ tacker vim-list |grep -E '(vim-yanxa2|tenant_id)'
| id | tenant_id | name | type | is_default | placement_attr | status |
| 45fa8c72-a127-48ac-9549-04decf7cd476 | 56c4a3d5240b41ef8e39b5e3b8a85605 | vim-yanxa2 | openstack | False | {u'regions': [u'RegionOne']} | REACHABLE |
| ce62645b-accf-49bc-9859-08c81c98be10 | 56c4a3d5240b41ef8e39b5e3b8a85605 | vim-yanxa2 | openstack | False | {u'regions': [u'RegionOne']} | REACHABLE |
According to the constraint of VIM, we should not have two vim with same names.
__table_args__ = (
schema.UniqueConstraint(
"tenant_id",
"name",
"deleted_at",
name="uniq_vim0tenant_id0name0deleted_at"),
)
This issue occurred after [1].
In that patch, We had introduce the unique constraint over name, tenant_id and deleted_at column. Where default value of deleted_at is NULL. The main point is Creating unique constraint over nullable key, actually destroy the property of uniqueness, and this bug occurred.
[1]: https:/