Deleting failed replication backup can hide error
Deleting failed replication backup can hide error

If there is a problem with getting the replication snapshot, the backup
is deleted. If the delete fails (if, for example, the backup is in the
wrong state) then the original exception is lost (and more importantly,
not logged).

Handling is now in place to trap exceptions while deleting a 'bad'
replication backup. All exceptions are logged and re-thrown as a
TroveError.

The duplicated code around the backup delete has also been collapsed
into one (nested) exception.

Change-Id: I858df7fd7eeb79dd1d559c4dd4b2851f7d0e0d98
Closes-Bug: #1386901

openstack/trove,redhat-openstack/trove,openstack/trove,fabian4/trove,mmasaki/trove,hplustree/trove,mmasaki/trove,zhangg/trove,cp16net/trove,zhujzhuo/openstack-trove,cp16net/trove,mmasaki/trove,zhujzhuo/openstack-trove,fabian4/trove,zhujzhuo/openstack-trove,zhangg/trove,hplustree/trove,cp16net/trove,fabian4/trove,redhat-openstack/trove,redhat-openstack/trove