Bug 1494039

Summary: OSD containers don't start after reboot
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: seb
Component: Ceph-AnsibleAssignee: Sébastien Han <shan>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: adeza, aschoen, ceph-eng-bugs, ceph-qe-bugs, gmeno, hnallurv, kdreyer, nthomas, sankarshan
Target Milestone: rc   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.0.0-0.1.rc11.el7cp Ubuntu: ceph-ansible_3.0.0~rc11-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:44: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:

Description seb 2017-09-21 11:35:59 UTC 
Description of problem:

osd doesn't start after reboot

Version-Release number of selected component (if applicable):


How reproducible:

reboot a server

Steps to Reproduce:
1.
2.
3.

Actual results:

osd down

Expected results:

osd up

Additional info:

It's sad but we can not rely on the prepare container anymore since the
log are flushed after reboot. So inpecting the container does not return
anything.
Now, instead we use a ephemeral container to look up for the
journal/block.db/block.wal (depending if filestore or bluestore) and
build the activate command accordingly.
Comment 6 Vasishta 2017-10-17 14:36:05 UTC 
Tried using ceph-ansible-3.0.2-1.el7cp.noarch, tried rebooting filestore - dmcrypt (true&false), colocated and dedicated journal OSDs, working fine, moving to VERIFIED state.

Regards,
Vasishta
Comment 9 errata-xmlrpc 2017-12-05 23:44: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