This didn't matter on master/jewel, but in hammer, keyvaluestore
asserts that gen != NO_GEN => shard != NO_SHARD.
Signed-off-by: Samuel Just <sjust@redhat.com>
ghobject_t test_obj = generate_long_name(319);
ghobject_t test_obj_2 = test_obj;
test_obj_2.generation = 0;
+ test_obj_2.shard_id = shard_id_t(0);
{
ObjectStore::Transaction t;
// should cause a split
available_objects.erase(old_obj);
ghobject_t new_obj = old_obj;
new_obj.generation++;
+ new_obj.shard_id = shard_id_t(0);
available_objects.erase(new_obj);
ObjectStore::Transaction *t = new ObjectStore::Transaction;