Project

General

Profile

Bug #47771

rgw: allow rgw-orphan-list to note when rados objects in namespace

Added by J. Eric Ivancich 4 months ago. Updated 3 months ago.

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

0%

Source:
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

Currently namespaces and locators are ignored when `rados ls` is run
to see RADOS's known objects. At this point we do not expect RGW data
objects to be in RADOS namespaces, so when that's detected, we'll
error out with a message. Additionally when objects have locators, we
will prevent their output from entering the .intermediate file.


Related issues

Related to rgw - Bug #47812: rgw: rgw-orphan-list should use "plain" formatted `rados ls` output Resolved
Copied to rgw - Backport #47816: nautilus: rgw: allow rgw-orphan-list to note when rados objects in namespace Resolved
Copied to rgw - Backport #47817: octopus: rgw: allow rgw-orphan-list to note when rados objects in namespace Resolved

History

#1 Updated by J. Eric Ivancich 4 months ago

  • Pull request ID set to 37572

#2 Updated by J. Eric Ivancich 4 months ago

  • Tracker changed from Fix to Bug
  • Regression set to No
  • Severity set to 3 - minor

#3 Updated by J. Eric Ivancich 4 months ago

  • Status changed from In Progress to Fix Under Review

#4 Updated by J. Eric Ivancich 4 months ago

  • Status changed from Fix Under Review to Pending Backport

#5 Updated by J. Eric Ivancich 4 months ago

  • Related to Bug #47812: rgw: rgw-orphan-list should use "plain" formatted `rados ls` output added

#6 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #47816: nautilus: rgw: allow rgw-orphan-list to note when rados objects in namespace added

#7 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #47817: octopus: rgw: allow rgw-orphan-list to note when rados objects in namespace added

#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