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 Jira Cloud for all bug tracking management.

Bug 1482579

Summary: introduce ceph-medic v1
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Ken Dreyer (Red Hat) <kdreyer>
Component: Ceph-MedicAssignee: Andrew Schoen <aschoen>
Status: CLOSED ERRATA QA Contact: Persona non grata <nobody+410372>
Severity: medium Docs Contact: Bara Ancincova <bancinco>
Priority: medium    
Version: 3.0CC: adeza, aschoen, ceph-qe-bugs, gmeno, hnallurv, vereddy
Target Milestone: rc   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-medic-1.0.2-1.el7cp Ubuntu: ceph-medic_1.0.2-2redhat1 Doc Type: Enhancement
Doc Text:
.A new `ceph-medic` utility A new utility, `ceph-medic`, is now available and fully supported. The utility detects common issues with a Ceph Storage Cluster that prevents the cluster from functioning properly. For details, see the https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/troubleshooting_guide/#installing-and-using-ceph-medic-to-diagnose-a-ceph-storage-cluster[Installing and Using ceph-medic to Diagnose a Ceph Storage Cluster] chapter in the Troubleshooting Guide for Red{nbsp}Hat Ceph Storage 3.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:39:47 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:
Bug Depends On:    
Bug Blocks: 1494421    

Description Ken Dreyer (Red Hat) 2017-08-17 15:52:43 UTC 
We are introducing a new package, ceph-medic, a tool for finding common issues in Ceph clusters.

On RHEL: yum install ceph-medic
On Ubuntu: apt-get install ceph-medic
Comment 9 errata-xmlrpc 2017-12-05 23:39:47 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-2017:3387