vavavr00m / boto

Automatically exported from code.google.com/p/boto
1 stars 0 forks source link

get_spot_price_history inconsistency / failure (SVN Trunk) #375

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. conn.get_spot_price_history(instance_type='m1.xlarge', 
end_time='2010-03-20T00:14:00.000Z', product_description='Linux/UNIX')

What is the expected output? What do you see instead?
The expected output is a consistent 3 entries (as shown by the 
ec2-describe-spot-price-history CLI tool when passed the same parameters)
What is shown instead is varied - sometimes the entries, sometimes nothing.

What version of the product are you using? On what operating system?
SVN Trunk, Rev 1589  (18May2010 checkout)

Please provide any additional information below.
I'm not sure what's causing this - I just started using boto tonight - is there 
a way to 'debug' or trace the requests?  I've submitted the same request a few 
seconds apart and gotten 
entirely different responses (as displayed at least).

From the python interpreter:

>>> conn.get_spot_price_history(instance_type='m1.xlarge', 
end_time='2010-03-20T01:14:45.000Z')[0].timestamp
u'2010-03-20T00:47:22.000Z'
>>> conn.get_spot_price_history(instance_type='m1.xlarge', 
end_time='2010-03-20T01:14:45.000Z')[0].timestamp
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
IndexError: list index out of range
>>> conn.get_spot_price_history(instance_type='m1.xlarge', 
end_time='2010-03-20T01:14:45.000Z')
[]

From the EC2 CLI tool:

adam@ubuntu:~/aws/boto-read-only$ ec2-describe-spot-price-history --end-time 
2010-03-20T01:14:45.000 --instance-type m1.xlarge -d Linux/UNIX
SPOTINSTANCEPRICE   0.233   2010-03-19T17:47:22-0800    m1.xlarge   Linux/UNIX
SPOTINSTANCEPRICE   0.249   2010-03-19T20:13:22-0800    m1.xlarge   Linux/UNIX
SPOTINSTANCEPRICE   0.232   2010-03-19T23:59:38-0800    m1.xlarge   Linux/UNIX

Original issue reported on code.google.com by upti...@gmail.com on 19 May 2010 at 1:32

GoogleCodeExporter commented 9 years ago
I'm not able to reproduce this problem.  When I call get_spot_price_history, I 
usually receive many (i.e. hundreds) of responses.  Are you still having this 
problem?

Original comment by Mitch.Ga...@gmail.com on 19 Jun 2010 at 12:11