DB repository calls in revert methods should have exception handling

[Michael Johnson]

There are a number of revert methods that make database repository calls without exception handling. This can lead to aborted revert flows. Granted, if the database is offline/unavailable we probably won't be successful with the remaining revert methods, but we should not be aborting the revert flows.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/371154

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/371154
Committed: https://git.openstack.org/cgit/openstack/octavia/commit/?id=fb6cc70b9668ff51ec4f915aa22ab5e05bcadea2
Submitter: Jenkins
Branch: master

commit fb6cc70b9668ff51ec4f915aa22ab5e05bcadea2
Author: Michael Johnson <email address hidden>
Date: Thu Sep 15 20:54:11 2016 +0000

    Fixes the revert methods with unhandled exceptions

    A number of the revert methods in our flow tasks make database
    repository calls but do not handle potential exceptions. This can
    lead to the revert flow aborting at these tasks.

    This patch adds exception handling to these repository calls inside
    the revert methods.

    Change-Id: Ia9b07890fe2c56382041175018679b87298c1b10
    Closes-Bug: #1624047

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/octavia 0.9.0 release.