Latest version of Typica causes error when instantiating/terminating instances in Eucalyptus

[GoogleCodeExporter]

What steps will reproduce the problem?

Instantiating/Terminating instances using "runInstance()", resp. 
"terminateInstance()" function calls causes a 
"com.xerox.amazonws.ec2.EC2Exception": Problem parsing returned message

What is the expected output? What do you see instead?
Instantiating/Terminating the instances w/o any errors.

What version of the product are you using? On what operating system?
Typica latest svn checkout r323 on a Ubuntu 9.10 machine. Eucalyptus 1.6.2 
(w/ lucid RC, but also occured in 1.6.0 on karmik)

Please provide any additional information below.
Each time an image is deployed in the UEC I always get the following 
Exceptions:

Exception in thread "main" com.xerox.amazonws.ec2.EC2Exception: Error while 
trying to generate new EC2 instance
    at CyclicRepeat.generateInstance(CyclicRepeat.java:92)
    at CyclicRepeat.main(CyclicRepeat.java:57)
Caused by: com.xerox.amazonws.ec2.EC2Exception: Problem parsing returned 
message.
    at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2290)
    at com.xerox.amazonws.ec2.Jec2.runInstances(Jec2.java:647)
    at com.xerox.amazonws.ec2.Jec2.runInstances(Jec2.java:625)
    at com.xerox.amazonws.ec2.Jec2.runInstances(Jec2.java:578)
    at CyclicRepeat.generateInstance(CyclicRepeat.java:84)
    ... 1 more
Caused by: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException: Content is not allowed in prolog.]
    at 
javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(Ab
stractUnmarshallerImpl.java:315)
    at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalEx
ception(UnmarshallerImpl.java:481)
    at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(Unmars
hallerImpl.java:199)
    at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(Unmarsh
allerImpl.java:168)
    at 
javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshal
lerImpl.java:137)
    at 
javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshal
lerImpl.java:184)
    at 
com.xerox.amazonws.common.JAXBuddy.deserializeXMLStream(JAXBuddy.java:80)
    at 
com.xerox.amazonws.common.AWSQueryConnection.createException(AWSQueryConnec
tion.java:701)
    at 
com.xerox.amazonws.common.AWSQueryConnection.makeRequest(AWSQueryConnection
.java:499)
    at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2286)
    ... 5 more
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
    at 
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseE
xception(ErrorHandlerWrapper.java:195)
    at 
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Erro
rHandlerWrapper.java:174)
    at 
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErr
orReporter.java:388)
    at 
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScan
ner.java:1414)
    at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver
.next(XMLDocumentScannerImpl.java:1039)
    at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocu
mentScannerImpl.java:648)
    at 
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNS
DocumentScannerImpl.java:140)
    at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scan
Document(XMLDocumentFragmentScannerImpl.java:510)
    at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Co
nfiguration.java:807)
    at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Co
nfiguration.java:737)
    at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:1
07)
    at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Abstract
SAXParser.java:1205)
    at 
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(S
AXParserImpl.java:522)
    at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(Unmars
hallerImpl.java:195)
    ... 12 more

I attached the error log of the Eucalyptus cloud controller.
The errors do not occur in the typica 1.6 release, but could not really 
figure out why these errors occur in the newer typica releases.

Original issue reported on code.google.com by clott...@googlemail.com on 26 Apr 2010 at 1:01

Attachments:

• errorlog.log

[GoogleCodeExporter]

Yes, I'm facing this issue, too.
The problem is that typica passes "LaunchSpecification.SecurityGroup.1 = 
yourgroup"
for the securitygroup parameter when contacting EC2/Eucalyptus. According to the
specs this should be "SecurityGroup.1 = yourgroup".

I've attached a patch :)

Original comment by frank.bi...@gmail.com on 30 Apr 2010 at 8:05

Attachments:

• runInstances.patch

[GoogleCodeExporter]

I've filed Issue #94 because it's not just with eucalypus, but may be the same 
cause
reading the previous comment

Original comment by carlossg on 20 May 2010 at 10:00

[GoogleCodeExporter]

I've fixed LaunchConfiguration where it sets up query params

Original comment by dkavan...@gmail.com on 4 Jun 2010 at 2:39

• Changed state: Fixed