Project

General

Profile

Actions

Bug #39261

closed

rgw: rgw-admin: search for user by access key

Added by Matt Benjamin about 5 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
easy first bug
Backport:
nautilus, mimic, luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Add or verify that there is already such a command in radosgw-admin.


Related issues 3 (0 open3 closed)

Copied to rgw - Backport #41119: nautilus: rgw: rgw-admin: search for user by access keyResolvedNathan CutlerActions
Copied to rgw - Backport #41120: mimic: rgw: rgw-admin: search for user by access keyResolvedNathan CutlerActions
Copied to rgw - Backport #41121: luminous: rgw: rgw-admin: search for user by access keyRejectedActions
Actions #1

Updated by hoan nv almost 5 years ago

i don't find this command in radosgw-admin.

Actions #2

Updated by Casey Bodley almost 5 years ago

this could be supported by extending 'radosgw-admin user info --access-key <key>', which currently requires a --uid argument

Actions #3

Updated by Matt Benjamin almost 5 years ago

  • Status changed from New to Fix Under Review
  • Assignee set to Matt Benjamin
  • Pull request ID set to 28331
Actions #4

Updated by Matt Benjamin almost 5 years ago

  • Backport set to nautilus, mimic, luminous
Actions #5

Updated by Matt Benjamin over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #6

Updated by Patrick Donnelly over 4 years ago

  • Copied to Backport #41119: nautilus: rgw: rgw-admin: search for user by access key added
Actions #7

Updated by Patrick Donnelly over 4 years ago

  • Copied to Backport #41120: mimic: rgw: rgw-admin: search for user by access key added
Actions #8

Updated by Patrick Donnelly over 4 years ago

  • Copied to Backport #41121: luminous: rgw: rgw-admin: search for user by access key added
Actions #10

Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF