Project

General

Profile

Feature #49275

[RFE] Add health warning in ceph status for filestore OSDs

Added by Prashant D over 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
-
% Done:

0%

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

Description

Along with health warn for filestore osds, the health detail should give OSD numbers which are still on filestore to drive end user to migrate filestore osds to bluestore.


Related issues

Copied to RADOS - Backport #54047: nautilus: [RFE] Add health warning in ceph status for filestore OSDs Rejected
Copied to RADOS - Backport #54048: octopus: [RFE] Add health warning in ceph status for filestore OSDs Rejected

History

#1 Updated by Prashant D over 2 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 39440

#2 Updated by Prashant D over 1 year ago

  • Status changed from Fix Under Review to Resolved

#3 Updated by Prashant D over 1 year ago

  • Status changed from Resolved to Pending Backport

#4 Updated by Backport Bot over 1 year ago

  • Copied to Backport #54047: nautilus: [RFE] Add health warning in ceph status for filestore OSDs added

#5 Updated by Backport Bot over 1 year ago

  • Copied to Backport #54048: octopus: [RFE] Add health warning in ceph status for filestore OSDs added

#6 Updated by Dan van der Ster over 1 year ago

Why is this being backported to N and O?!

Filestore is deprecated since quincy, so we should only warn in quincy and possibly pacific.

If backported to pacific, we should have clear ReleaseNotes about the new warning and how to switch it off.
(To me it seems unfriendly to the users to deprecate a feature during a bugfix release, but the warning in pacific would be intended to give an early heads up about the upcoming deprecation.)

#7 Updated by Konstantin Shalygin over 1 year ago

@Dan, I think maybe this is copy-paste issue?

#8 Updated by Prashant D over 1 year ago

  • Status changed from Pending Backport to Resolved

It was accidentally marked as pending backport. We are not backporting PR for this tracker to pre-quincy. Marking it resolved.

Also available in: Atom PDF