Bug 1977952

Summary: ceph crash ls shows no events when ceph-mon, osd, mgr processes are killed.
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Sridhar Venkat (IBM) <svenkat>
Component: cephAssignee: Scott Ostapovicz <sostapov>
Status: CLOSED DUPLICATE QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.8CC: bniver, jdurgin, madam, ocs-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: ppc64le   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-30 19:48:43 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 Sridhar Venkat (IBM) 2021-06-30 19:22:03 UTC
Description of problem (please be detailed as possible and provide log
snippets):
Deployed OCP and OCS 4.8. Then logged into a ocs worker node and killed ceph-mon/osd/mgr processes. Then checked ceph crash ls and do not see anything in it. Waiting for 600 seconds and still do not see anything in it.
This test was done on ppc64le environment.

Version of all relevant components (if applicable):
4.8


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No.

Is there any workaround available to the best of your knowledge?
No.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
N/A

If this is a regression, please provide more details to justify this:
Not known.

Steps to Reproduce:
1. See above.
2.
3.


Actual results:
Nothing in ceph crash ls output.


Expected results:
Entries in ceph crash ls output.


Additional info:

Comment 2 Josh Durgin 2021-06-30 19:48:43 UTC

*** This bug has been marked as a duplicate of bug 1975795 ***