Jakub Libosvar
26b3e6b1c4
RBAC network policy is uniquely identified by network ID. That means when attempting to create such network policy, we should not retry when such policy already exists in the database. Before we switched in rbac to use OVO, we translated DB DBDuplicateEntry on such ocasions into dedicated RBAC exception to avoid DB retry mechanism (see bug/1551473). After introducing OVO layer for RBAC, the exception was not changed to the one coming from OVO. This patch replaces the exception from DB to the exception from OVO. Another patch will go to neutron-tempest-plugin to limit time API needs to reply with failure to user, when attempting to create an existing policy. Closes-Bug: #1831647 Change-Id: I7c65376f6fd6fc29d510ea532a684917ed95deb1
Team and repository tags
Welcome!
To learn more about neutron:
- Documentation: https://docs.openstack.org
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute:
CONTRIBUTING.rst