GitHub user jadunham1 opened a pull request:
https://github.com/apache/libcloud/pull/692
Adding a new exception code/message, testing backup exceptions
The backup client bad responses have different XML responses than the
others.
<ns0:Status xmlns:ns0="http://oec.api.opsource.net/schemas/general";>
<ns0:operation>Enable Backup for Server</ns0:operation>
<ns0:result>ERROR</ns0:result>
<ns0:resultDetail>Cloud backup for this server is already enabled or
being enabled (state: NORMAL).</ns0:resultDetail>
<ns0:resultCode>REASON_550</ns0:resultCode>
</ns0:Status>
I added in handling for this and making it easier to create new bad xml
elements in case there are more later on.
Added tests to test the bad handling in the backup client
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jadunham1/libcloud feature/dd_handle_exception
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/692.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #692
----
commit 07658945a21039edef21190f422e93b02761bb02
Author: Jeffrey Dunham <[email protected]>
Date: 2016-02-06T17:11:31Z
Adding a new exception code/message, testing backup exceptions
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
