Bug 1578142

Summary: [cephfs]: MDS asserted while in Starting/resolve state
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Patrick Donnelly <pdonnell>
Component: CephFSAssignee: Patrick Donnelly <pdonnell>
Status: CLOSED ERRATA QA Contact: Ramakrishnan Periyasamy <rperiyas>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: ceph-eng-bugs, ceph-qe-bugs, edonnell, hnallurv, jbrier, john.spray, jquinn, kdreyer, pdonnell, rperiyas, tmuthami, zyan
Target Milestone: rc   
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.5-13.el7cp Ubuntu: 12.2.5-4redhat1xenial Doc Type: Bug Fix
Doc Text:
.MDS no longer asserts while in starting/resolve state Previously, when increasing "max_mds" from "1" to "2", if the Metadata Server (MDS) daemon was in the starting/resolve state for a long period of time, then restarting the MDS daemon led to an assert. This caused the Ceph File System (CephFS) to enter a degraded state. With this update to {product}, the underlying issue has been fixed, and increasing "max_mds" no longer causes CephFS to enter a degraded state.
 Story Points: ---
Clone Of: 1566016 Environment:
Last Closed: 2018-09-26 18:20:21 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: 1566016    
Bug Blocks: 1557269, 1584264    

Comment 10 Ramakrishnan Periyasamy 2018-07-12 08:51:55 UTC 
Moving this bug to verified state.

Not observed any MDS crash during Cluster upgrade and MDS in starting/stopping state.

Automation Regression suite run: http://cistatus.ceph.redhat.com/ui/#cephci/launches/all%7Cpage.page=2&page.size=50&page.sort=start_time,number%2CDESC/5b3f836536d1a00001ee66e0?page.page=1&page.size=50&page.sort=start_time%2CASC
Comment 15 errata-xmlrpc 2018-09-26 18:20:21 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-2018:2819