Bug #19904
Updated by Orit Wasserman about 7 years ago
Steps to Reproduce: 1. Create bucket with '_' using swift 2. Let the bucket sync 3. Create objects in it. Check if it syncs We are failing to sync the bucket instance: { "id": "1_1494428689.370173_1208544.1", "section": "data", "name": "__test__:e57026aa-45e4-48fb-9cd3-b51bdd792a2a.292866.4", "timestamp": "2017-05-10 15:04:49.370173Z", "info": { "source_zone": "e57026aa-45e4-48fb-9cd3-b51bdd792a2a", "error_code": 22, "message": "failed to sync bucket instance: (22) Invalid argument" } }, in the master: __test__?versions 2017-05-10 15:00:36.284440 7f49f4ff1700 15 calculated digest=LnXfLGVwpdXJfyimYnPdPIPXu0w= 2017-05-10 15:00:36.284441 7f49f4ff1700 15 auth_sign=LnXfLGVwpdXJfyimYnPdPIPXu0w= 2017-05-10 15:00:36.284442 7f49f4ff1700 15 compare=0 2017-05-10 15:00:36.284443 7f49f4ff1700 20 system request 2017-05-10 15:00:36.284447 7f49f4ff1700 2 req 7759:0.000109:s3:GET /__test__:list_bucket:normalizing buckets and tenants 2017-05-10 15:00:36.284450 7f49f4ff1700 10 s->object=<NULL> s->bucket=__test__ 2017-05-10 15:00:36.284452 7f49f4ff1700 10 failed to run post-auth init 2017-05-10 15:00:36.284453 7f49f4ff1700 20 op->ERRORHANDLER: err_no=-2000 new_err_no=-2000 2017-05-10 15:00:36.284508 7f49f4ff1700 2 req 7759:0.000170:s3:GET /__test__:list_bucket:op status=0 2017-05-10 15:00:36.284516 7f49f4ff1700 2 req 7759:0.000178:s3:GET /__test__:list_bucket:http status=400 2017-05-10 15:00:36.284519 7f49f4ff1700 1 ====== req done req=0x7f49f4feb710 op status=0 http_status=400 ======