erasure-code: unfound test needs a non empty file

Other rados put will fail as follows

$ touch /tmp/bar
$ ./rados -p rbd put existing_3 /tmp/bar
$ ./rados -p rbd put existing_3 /tmp/bar
WARNING: could not create object: existing_3
error putting rbd/existing_3: (17) File exists

it should be considered a bug in the rados command line but needs to be
addressed separately.

http://tracker.ceph.com/issues/9387 Fixes: #9387

Signed-off-by: Loic Dachary loic-201408@dachary.org
This commit is contained in:
Loic Dachary 2014-10-02 08:06:42 +02:00
parent 7a2df8d0c2
commit e48a0a3924

View File

@ -42,8 +42,8 @@ def task(ctx, config):
manager.create_erasure_code_profile(profile_name, profile)
pool = manager.create_pool_with_unique_name(erasure_code_profile_name=profile_name)
# something that is always there
dummyfile = '/etc/fstab'
# something that is always there, readable and never empty
dummyfile = '/etc/group'
# kludge to make sure they get a map
rados(ctx, mon, ['-p', pool, 'put', 'dummy', dummyfile])