Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1636627

Summary:	Some cephfs tool commands silently operate on only rank 0, even if multiple ranks exist
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Patrick Donnelly <pdonnell>
Component:	CephFS	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED ERRATA	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.0	CC:	ceph-eng-bugs, rperiyas, tserlin
Target Milestone:	z1	Keywords:	CodeChange
Target Release:	3.2
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.8-64.el7cp Ubuntu: ceph_12.2.8-49redhat1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-07 15:50:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Patrick Donnelly 2018-10-05 22:27:51 UTC

Description of problem:

> We made commands like cephfs-journal-tool operate on rank 0 by default, at a time when single MDS systems were the norm.

> On a system with many MDS ranks, it is confusing to run this command, see it succeed, but have it only act on one rank. Maybe we should change the default to all ranks, or maybe we should warn the user that they're only acting on one, but the current silent behaviour is a bit awkward.

> We could get rid of the default option entirely, as it is also kind of scary that these commands will operate (I think?) on the default filesystem when there are multiple filesystems, which makes it easy for someone to forget they have multiple filesystems, and do a "reset" on a particular rank forgetting which one they're acting on.

Comment 10 errata-xmlrpc 2019-03-07 15:50:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0475