Project

General

Profile

Bug #40991

rgw: potential realm watch lost

Added by Tianshan Qu over 1 year ago. Updated 3 months ago.

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

0%

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

Description

realm watch only restart on -ENOTCONN, but if we fail to maintain the watch ping, the OSD will return -ETIMEDOUT.
the objecter will keep the last_error, if we not handle it, it will not call handle_error in future error. so it will never get the chance to rewatch on following -ENOTCONN error.


Related issues

Copied to rgw - Backport #41481: luminous: rgw: potential realm watch lost Rejected
Copied to rgw - Backport #41482: nautilus: rgw: potential realm watch lost Resolved
Copied to rgw - Backport #41483: mimic: rgw: potential realm watch lost Resolved

History

#2 Updated by Casey Bodley over 1 year ago

  • Status changed from New to 7

#3 Updated by Casey Bodley over 1 year ago

  • Pull request ID set to 29369

#4 Updated by Casey Bodley over 1 year ago

  • Status changed from 7 to Pending Backport
  • Backport set to luminous mimic nautilus

#5 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #41481: luminous: rgw: potential realm watch lost added

#6 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #41482: nautilus: rgw: potential realm watch lost added

#7 Updated by Nathan Cutler over 1 year ago

#8 Updated by Nathan Cutler 3 months 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".

Also available in: Atom PDF