Project

General

Profile

Actions

Bug #53941

closed

Trim thread crashes when cluster misconfigured to have empty endpoints

Added by Adam Emerson about 2 years ago. Updated about 1 year ago.

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

100%

Source:
Q/A
Tags:
Backport:
pacific, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

A zone with empty endpoints should print an error and bail out of the sync thread rather than crashing.


Related issues 3 (0 open3 closed)

Copied to rgw - Backport #53973: Trim thread crashes when cluster misconfigured to have empty endpointsResolvedAdam EmersonActions
Copied to rgw - Backport #54037: octopus: Trim thread crashes when cluster misconfigured to have empty endpointsRejectedActions
Copied to rgw - Backport #54038: pacific: Trim thread crashes when cluster misconfigured to have empty endpointsRejectedActions
Actions #1

Updated by Adam Emerson about 2 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 44674
Actions #2

Updated by Adam Emerson about 2 years ago

  • Backport changed from pacific, octopus, nautilus to quincy, pacific, octopus, nautilus
Actions #3

Updated by Adam Emerson about 2 years ago

  • Copied to Backport #53973: Trim thread crashes when cluster misconfigured to have empty endpoints added
Actions #4

Updated by Casey Bodley about 2 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport changed from quincy, pacific, octopus, nautilus to pacific, octopus
Actions #5

Updated by Backport Bot about 2 years ago

  • Copied to Backport #54037: octopus: Trim thread crashes when cluster misconfigured to have empty endpoints added
Actions #6

Updated by Backport Bot about 2 years ago

  • Copied to Backport #54038: pacific: Trim thread crashes when cluster misconfigured to have empty endpoints added
Actions #8

Updated by Adam Emerson over 1 year ago

  • Status changed from Pending Backport to Resolved
Actions #9

Updated by Konstantin Shalygin about 1 year ago

  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF