{"push_id":1001647163,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"9d691b972a46ad60d41ceacd8ccb3cf7ac06b5f3","before":"37967561f001768bc76705cc75409ada8882ef71","commits":[{"sha":"d9a18b04498f68a4efe859d0a032ea1c3e825dd6","author":{"email":"4cec69a2e3f23b658ef5550bf7c5b5012f9473f7@hpe.com","name":"Andrea Frittoli (andreaf)"},"message":"Properly handle failures during resource cleanup\n\nThe current code that cleans-up network resouces from the dynamic\ncredentials provider does not account for failures during the\ncleanup itself (apart from 404).\n\nWhen the cleanup is triggered by a failure during the setup, the\noriginal failure is hidden which makes debugging impossible.\n\nCatching all exceptions on cleanup, logging a warning and\nre-rasing the original exception should fix that.\n\nFixes bug 1551264\n\nChange-Id: I49dbb314a09fd9b49c9604bc8b5b8ed03ff218d4","distinct":true,"url":"https://api.github.com/repos/openstack/tempest/commits/d9a18b04498f68a4efe859d0a032ea1c3e825dd6"},{"sha":"9d691b972a46ad60d41ceacd8ccb3cf7ac06b5f3","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Properly handle failures during resource cleanup\"","distinct":true,"url":"https://api.github.com/repos/openstack/tempest/commits/9d691b972a46ad60d41ceacd8ccb3cf7ac06b5f3"}]}