Project

General

Profile

Actions
Copy link

Bug #37527

closed

librgw not sync s3 user info since started

Added by Tao CHEN over 5 years ago. Updated about 3 years ago.

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

0%

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

Description

Hi, I'm using NFS over RGW and I found that the change of user's quota will not be applied since librgw init. Should we update regularly?

Related issues 2 (0 open — 2 closed)

Copied to rgw - Backport #37548: mimic: librgw not sync s3 user info since startedResolvedPrashant DActions
Copied to rgw - Backport #37549: luminous: librgw not sync s3 user info since startedResolvedPrashant DActions
Actions
Copy link
 #1

Updated by Brad Hubbard over 5 years ago

  • Project changed from Ceph to rgw
Actions
Copy link
 #3

Updated by Casey Bodley over 5 years ago

  • Status changed from New to 7
Actions
Copy link
 #4

Updated by Casey Bodley over 5 years ago

  • Status changed from 7 to Pending Backport
  • Backport set to mimic luminous
Actions
Copy link
 #5

Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #37548: mimic: librgw not sync s3 user info since started added
Actions
Copy link
 #6

Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #37549: luminous: librgw not sync s3 user info since started added
Actions
Copy link
 #7

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
Copy link

Also available in: Atom PDF