[Bug 962046] Re: EC2 metadata retrieval fails with spaces in a resource name

[Edward Hope-Morley]

updated SRU testcase and added debdiff for Raring

** Description changed:

  [Impact]
  
  Example when using a key name 'my key':
  
  Caught exception reading instance data:
  http://169.254.169.254/2009-04-04/meta-data/mpi/my key
  
  Is a boto issue, see https://github.com/boto/boto/issues/659
  
+ Patches provided for Precise, Quantal and Raring. Fix already exists in
+ Saucy.
  
  [Test Case]
  
+ There are two ways to test this. The first provides that the change will affect
+ the url in the required manner but does not test the package. The second will
+ test the package but needs to be run within an Openstack instance against an
+ API that has calls with spaces on their name.
+ 
+ ====
+ #!/usr/bin/env python
+ import urllib
+ 
+ resource = "http://169.254.169.254/2009-04-04/meta-data/i love spaces"
+ print "unsafe: %s" % resource
+ 
+ resource = urllib.quote(resource, safe="/:")
+ print "safe: %s" % resource
+ 
+ ===
  #!/usr/bin/env python
  from boto import utils
  utils.get_instance_metadata()
  
+ 
  [Regression Potential]
-  This is a very low risk change. It has been tested on Precise. A quantal patch is also provided.
+  This is a very low risk change. It has been tested on Precise. A quantal patch is also provided.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-boto in Ubuntu.
https://bugs.launchpad.net/bugs/962046

Title:
  EC2 metadata retrieval fails with spaces in a resource name

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/962046/+subscriptions