Project

General

Profile

Bug #52748

specifing --tags、--placement-id and --storage-class are not work when create(modify) user

Added by Huber ming 2 months ago. Updated about 2 months ago.

Status:
Won't Fix - EOL
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
placement
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

when I create and modify a user's default_placement/default_storage_class/placement_tags by specifing --placement-id、 --storage-class and --tags, but it is does not work.
radosgw version 14.2.15

History

#1 Updated by Casey Bodley about 2 months ago

  • Assignee set to Casey Bodley

#2 Updated by Casey Bodley about 2 months ago

  • Status changed from New to Need More Info
  • Tags set to placement

hi, can you please clarify which part doesn't work?

after adding a new storage class 'GLACIER' to the zonegroup and zone and restarting radosgw, i'm able to modify a user with '--storage-class GLACIER'. after creating a new bucket with that user, i verified with 'radosgw-admin bucket stats' that it has "placement_rule": "default-placement/GLACIER"

were you maybe expecting these user defaults to take effect on existing buckets? they only apply during the creation of new buckets

#3 Updated by Huber ming about 2 months ago

are you sure radosgw-admin version is 14.2.15 ?
the value of "placement_tags" is not changed after running "radosgw-admin user modify --uid {uid} --tags={tags}"

#4 Updated by Casey Bodley about 2 months ago

  • Status changed from Need More Info to Won't Fix - EOL

Huber ming wrote:

are you sure radosgw-admin version is 14.2.15 ?

sorry no, this was testing on master. it looks like this stuff wasn't implemented until https://github.com/ceph/ceph/pull/31185, which landed just before octopus. since nautilus is end-of-life, it won't be getting this change

Also available in: Atom PDF