Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 451140 - EC2 gahp needs to handle SOAP 1.2 along with 1.1 faults
Summary: EC2 gahp needs to handle SOAP 1.2 along with 1.1 faults
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: 2.0
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-12 22:52 UTC by Matthew Farrellee
Modified: 2011-01-07 17:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-01-07 17:57:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Matthew Farrellee 2008-06-12 22:52:59 UTC
Example SOAP 1.2:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xml:lang="en-US">Request could not be executed due to an internal service

How the EC2 gahp parses it:

6/12 16:04:00 Call to DeleteKeyPair failed: SOAP 1.2 fault: SOAP-ENV:Receiver
"Request could not be executed due to an internal service error"
Detail: <aws:RequestId

6/12 16:04:00 Command(AMAZON_VM_DESTROY_KEYPAIR) got error(code:Receiver,
msg:Request could not be executed due to an internal service error
6/12 16:04:00 CMD("AMAZON_VM_DESTROY_KEYPAIR 1179 ...) is done with result 1179
1 Receiver Request\ could\ not\ be\ executed\ due\ to\ an\ internal\ service\ error

The result should be:

1179 1 InternalError Request\ could...


Example of SOAP 1.1

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
instance(s) are already running.</faultstring><detail><aws:RequestId

It is properly parsed: 

6/12 15:50:51 Call to RunInstances failed: SOAP 1.1 fault:
[no subcode]
"20 instance(s) are already running."
Detail: <aws:RequestId

6/12 15:50:51 Command(AMAZON_VM_START) got error(code:InstanceLimitExceeded,
msg:20 instance(s) are already running.
6/12 15:50:51 CMD("AMAZON_VM_START 44 ...") is done with result 44 1
InstanceLimitExceeded 20\ instance(s)\ are\ already\ running.


Example of SOAP 1.1, with a problem

(xml unavailable)

The fault code here is problematic because it doesn't exist, there's just a
message, e.g. code = Client not Client.TryAgain

6/12 12:33:12 Call to CreateKeyPair failed: SOAP 1.1 fault: SOAP-ENV:Client [no 
"Try Again"
Detail: get host by name failed in tcp_connect()

6/12 12:33:12 Command(AMAZON_VM_CREATE_KEYPAIR) got error(code:Client, msg:Try A
6/12 12:33:12 CMD("AMAZON_VM_CREATE_KEYPAIR 51 ...") is done
with result 51 1 Client Try\ Again

NOTE: Even with this fault to try again, the key pair was created!

NOTE2: This fault may be coming from gSOAP itself, and should be handled differently


Another example error, no xml

6/10 15:15:12 Call to DescribeInstance failed: SOAP 1.1 fault:
"http://webservices.amazon.com/AWSFault/2005-15-09":Client.InvalidSecurity [no
"Request has expired"
Detail: <aws:RequestId

6/10 15:15:12 Command(AMAZON_VM_STATUS) got error(code:InvalidSecurity,
msg:Request has expired
6/10 15:15:12 CMD("AMAZON_VM_STATUS 64 ...") is done with result 64 1
InvalidSecurity Request\ has\ expired

Comment 1 Matthew Farrellee 2011-01-07 17:57:09 UTC
If this appears again or more frequently it can be re-opened.

Note You need to log in before you can comment on or make changes to this bug.