Bug #16736
openrgw: a bucket with non-empty tenant can't link to specified user
0%
Description
a bucket create under a user with tenant can't link to other user, and a bucket create under a user without tenant can't link to user with tenant too.
[root@c49 ~]# radosgw-admin bucket stats --bucket=111\/BUCKET_111
{
"bucket": "BUCKET_111",
"pool": "default.rgw.buckets.data",
"index_pool": "default.rgw.buckets.index",
"id": "6b185469-312a-45f9-bf68-5fa8316625f3.24107.1",
"marker": "6b185469-312a-45f9-bf68-5fa8316625f3.24107.1",
"owner": "111$test222",
"ver": "0#1",
"master_ver": "0#0",
"mtime": "2016-07-19 14:09:26.217213",
"max_marker": "0#",
"usage": {},
"bucket_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
}
}
[root@c49 ~]# radosgw-admin bucket link --bucket=111\/BUCKET_111 --bucket-id=6b185469-312a-45f9-bf68-5fa8316625f3.24107.1 --uid=111
failure: (2) No such file or directory:
[root@c49 ~]# radosgw-admin bucket stats --bucket=BUCKET_aaa
{
"bucket": "BUCKET_aaa",
"pool": "default.rgw.buckets.data",
"index_pool": "default.rgw.buckets.index",
"id": "6b185469-312a-45f9-bf68-5fa8316625f3.4303.1",
"marker": "6b185469-312a-45f9-bf68-5fa8316625f3.4303.1",
"owner": "111",
"ver": "0#29",
"master_ver": "0#0",
"mtime": "2016-07-19 16:22:21.996426",
"max_marker": "0#",
"usage": {
"rgw.main": {
"size": 2930,
"size_actual": 16384,
"size_kb": 3,
"size_kb_actual": 16,
"num_objects": 4
}
},
"bucket_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
}
}
[root@c49 ~]# radosgw-admin bucket link --bucket=BUCKET_aaa --bucket-id=6b185469-312a-45f9-bf68-5fa8316625f3.4303.1 --uid=111\$test222
failure: (2) No such file or directory:
2016-07-19 16:22:48.867782 7faa73917400 0 could not get bucket info for bucket=BUCKET_aaa
I not sure this is a bug or a future of rgw
Updated by Bastian Rosner about 7 years ago
I can confirm that this issue also exists in most recent kraken release.
This unfortunately makes working in a multi-tenant environment quite complicated. Changing ownership of buckets from one tenantA$userA to another tenantB$userB has to be possible via admin API.
Updated by Yehuda Sadeh about 7 years ago
Yeah, currently the problem is that bucket instance id includes the tenant. Changing it is problematic, because it can and will break existing data.
Updated by Matt Benjamin about 7 years ago
- Status changed from New to 12
- Assignee set to Matt Benjamin
triage: need forward progress for Luminous; policies will be available; need more discussion by 3/16