Description of problem: Objects that were created prior to Hammer that start with underscore cannot be accessed anymore. They are still listed, but cannot be found. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create object with name that starts with underscore (on pre-Hammer release) 2. Upgrade to Hammer 3. Access object Actual results: 404 response Expected results: 200 response Additional info: The culprit is an unintended behavior of the old code that is related to the rados object locator.
Should this block the 1.3.0 release, or should ship a fix after 1.3.0 ships?
Is this going to be fixed in 1.3.0? If going to be fixed in 1.3.0 then the test plan for this fix is that repeat the steps mentioned above while upgrading from 1.2* to 1.3.0. If this plan is incorrect please let QE know.
Yes, this is going to be fixed in 1.3.0.
The QE test plan for this fix is: Repeat the steps mentioned in "Steps to Reproduce" while upgrading from 1.2* to 1.3.0. If this plan is incorrect then please let QE know the right plan.
yes
Upgrade is failing - Once it gets fixed, I will be able to verify .. Depends on :- 1227358 & 1230832
[root@magna116 conf.d]# cat s3test.py import boto import boto.s3.connection access_key = 'AM67GV605FNDBZ57TSLF' secret_key = 'Q0eCc/oYm+AooD1VeraqfrAqS7abK5++ll55n7vW' conn = boto.connect_s3( aws_access_key_id = access_key, aws_secret_access_key = secret_key, host = 'magna116', is_secure=False, calling_format = boto.s3.connection.OrdinaryCallingFormat(), ) #bucket = conn.create_bucket('testt-bucket') for bucket in conn.get_all_buckets(): print "{name}\t{created}".format( name = bucket.name, created = bucket.creation_date, ) #key = bucket.new_key('hello_hem.txt') #key.set_contents_from_string('Hello World!') #hello_key = bucket.get_key('hello_hem.txt') #hello_key.set_canned_acl('public-read') #key = bucket.new_key('_hello_hem.txt') #key.set_contents_from_string('Hello ') key = bucket.get_key('_hello_hem.txt') key.get_contents_to_filename('/etc/httpd/conf.d/_hello_hem.txt') [root@magna116 conf.d]# python s3test.py testt-bucket 2015-06-11T11:34:52.000Z [root@magna116 conf.d]# ls autoindex.conf fastcgi.conf _hello_hem.txt README rgw.conf s3test.py ssl.conf userdir.conf welcome.conf [root@magna116 conf.d]# cksum _hello_hem.txt 1904456389 6 _hello_hem.txt [root@magna116 conf.d]# On the OSD Node :- [root@gqas006 13.5_head]# cksum default.13418.1\\u\\u\\uhello\\uhem.txt_default.13418.1\\u\\uhello\\uhem.txt_head_BBFE29E5__d 1904456389 6 default.13418.1\u\u\uhello\uhem.txt_default.13418.1\u\uhello\uhem.txt_head_BBFE29E5__d I was able to access/download the object file with "_" and also verified the cksum of both the files.. It was Fine Moving to verified state
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2015:1183