Comment 3 for bug 948595

Johannes- The bug is that it does not route anywhere. AFAICS, its in the list (with the rest of the versions reported) to maintain ec2 compatibility. In fat, I came across the issue when testing a tool designed for EC2 on nova.

On EC2, for example:

adam@ath0:~$ curl http://169.254.169.254/
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
2011-01-01
2011-05-01
latest
adam@ath0:~$ curl http://169.254.169.254/1.0/
meta-data
user-data
adam@ath0:~$ curl http://169.254.169.254/1.0/meta-data/
ami-id
ami-launch-index
ami-manifest-path
hostname
instance-id
local-ipv4
public-keys/
reservation-id
security-groups
adam@ath0:~$