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.
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
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