7ca02243d1
When the VIM Stragegy API returns a 409 Conflict for a create, it is much more useful to know details about the conflict. ie: what type of strategy already exists. This fix required: - the strategy creation rpc message adds an error string - pecan.abort 'conflict' must include the error string - the nfv_client code must extract the error string - the strategy types must return knowledge of an existing strategy type - the director class must include details of the existing strategy type in its failure messages. Test Plan: PASS: Create two patch strategies and view the error. PASS: Create two different strategies and view the error. PASS: View errors when creating multiple strategies from horizon. Closes-Bug: #1989485 Signed-off-by: Al Bailey <al.bailey@windriver.com> Change-Id: Ic79eab03b70b8bc7fbe2876f95eea3f2f34ab791 |
||
---|---|---|
.. | ||
acl | ||
controllers | ||
openstack | ||
__init__.py | ||
_application.py | ||
_config.py | ||
_hooks.py | ||
_link.py |