Project

General

Profile

Actions

Feature #38029

closed

[RFE] If the nodeep-scrub/noscrub flags are set in pools instead of global cluster. List the pool names in the ceph status

Added by Vikhyat Umrao about 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Mohamad Gebai
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus
Reviewed:
Affected Versions:
Component(RADOS):
Pull request ID:

Description

[RFE] If the nodeep-scrub/noscrub flags are set in pools instead of global cluster. List the pool names in the ceph status which have these flags set.

Ceph has noscrub and nodeep-scrub flags which we can now set at pool level as compared to global cluster. This came in jewel release now what happens when we set these flags globally
like `ceph osd set nodeep-scrub` and `ceph osd set noscrub` they are visible in `ceph -s` but when we set them at pool level they are not visible in `ceph -s` and if users/admin might set them and forgot that they have ever set them we will have some pools always scrub and deep-scrub disabled until we notice them with `ceph osd pool ls detail` command.

RHBZ - https://bugzilla.redhat.com/show_bug.cgi?id=1581421


Related issues 1 (0 open1 closed)

Copied to RADOS - Backport #39700: nautilus: [RFE] If the nodeep-scrub/noscrub flags are set in pools instead of global cluster. List the pool names in the ceph statusResolvedNathan CutlerActions
Actions #1

Updated by Mohamad Gebai about 5 years ago

  • Assignee set to Mohamad Gebai
Actions #2

Updated by Neha Ojha about 5 years ago

  • Status changed from New to Fix Under Review
Actions #3

Updated by Vikhyat Umrao almost 5 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to nautilus
Actions #4

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #39700: nautilus: [RFE] If the nodeep-scrub/noscrub flags are set in pools instead of global cluster. List the pool names in the ceph status added
Actions #5

Updated by Nathan Cutler over 4 years ago

  • Pull request ID set to 26488
Actions #6

Updated by Nathan Cutler over 4 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