Hi Romil -
There are many places in delete_xxx_postcommit() mechanism drivers where exceptions are taken. Today all the MD exceptions get mapped to the ML2 common exception MechasnismDriverError and in the case of delete_xxx_postcommit() methods these exceptions are only logged (see plugin.py: delete_network,subnet,port methods).
Hi Romil - xxx_postcommit( ) mechanism drivers where exceptions are taken. Today all the MD exceptions get mapped to the ML2 common exception MechasnismDrive rError and in the case of delete_ xxx_postcommit( ) methods these exceptions are only logged (see plugin.py: delete_ network, subnet, port methods).
There are many places in delete_
There's been other investigations in this general area (i.e. error reporting inside of ML2, specifically for MDs): /etherpad. openstack. org/p/ML2_ Juno_Roadmap /review. openstack. org/#/c/ 69748/6 /wiki.openstack .org/wiki/ NovaInstanceAct ions
https:/
- See "ML2 Driver Error handling and recovery - ML2 Sync:" section
- https:/
During this review (see comments) it was recommended that an approach similar to Nova be implemented:
https:/
I don't think that you could work on this bug without finding out the current status of how the overall ML2 error reporting design may be changed.
Thanks, Rich