Comment 9 for bug 721297

Ok, with the fix I just pushed (#705), I now get:

2011-02-21 14:20:25,790 DEBUG nova.api.request [-] <?xml version="1.0" ?><RunInstancesResponse xmlns="http://ec2.amazonaws.com/doc/2009-11-30/"><requestId>IDGIWP-7CJ9292AFG6RP</requestId><ownerId>mtbcal</ownerId><groupSet><item><groupId>default</groupId></item></groupSet><reservationId>r-xgnisy5c</reservationId><instancesSet><item><displayDescription/><displayName>Server 6</displayName><keyName>pk.pem (mtbcal, None)</keyName><instanceId>i-00000006</instanceId><instanceState><code/><name>scheduling</name></instanceState><publicDnsName/><imageId>ami-5b5mum3v</imageId><productCodesSet/><privateDnsName/><dnsName/><launchTime>2011-02-21T22:20:25Z</launchTime><placement><availabilityZone>unknown zone</availabilityZone></placement><amiLaunchIndex>0</amiLaunchIndex><instanceType>m1.small</instanceType></item></instancesSet></RunInstancesResponse> from MainProcess (pid=30279) _render_response /home/kpepple/src/nova/lp721297/nova/api/ec2/apirequest.py:155

when i do a euca-run-instance. I believe "<launchTime>2011-02-21T22:20:25Z</launchTime>" is the format you need.

I've also added a small test to prevent regressions on this.

Can you test this (need to $lp merge lp:~ken-pepple/nova/lp721297) and report back ?
If it doesn't work, can you write a simple test using that SDK that I can test against ?