
Checked all cases of re-raised exceptions. In several cases, the exception was redundant (re-raising the same exception), so the try block and exception handling was removed. In one case, exceptions raised from two sources were re-raised with a a different exception. Instead of doing this, the original exceptions were changed and the try block and re-raised exception were removed. In cases where there were database exceptions that were re-raised as Neutron exceptions, the traceback was left as-is, since it was more informative to know the higher level source of the issue. The same was true for the exception mentioned in the bug, where the original failure was in the ncclient library parsing the configuration and it would be more descriptive to know that there was a connection failure or a config failure, that to know the library method. bug 1213159 Change-Id: Ie334d2548bf651c61e878bf797adaf8c5880eb86
Cisco Neutron Virtual Network Plugin This plugin implements Neutron v2 APIs and helps configure topologies consisting of virtual and physical switches. For more details on use please refer to: http://wiki.openstack.org/cisco-neutron