https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2017-01-31T08:21:21ZCeph Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=852162017-01-31T08:21:21ZNathan Cutlerncutler@suse.cz
<ul></ul><p>Did you apply <a class="external" href="https://github.com/ceph/ceph/pull/12147">https://github.com/ceph/ceph/pull/12147</a> as well?</p> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=852172017-01-31T09:35:16ZAlexey Sheplyakovasheplyakov@mirantis.com
<ul></ul><blockquote>
<p>Did you apply <a class="external" href="https://github.com/ceph/ceph/pull/12147">https://github.com/ceph/ceph/pull/12147</a> as well?</p>
</blockquote>
<p>Yes.</p> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=852182017-01-31T10:06:39ZAlexey Sheplyakovasheplyakov@mirantis.com
<ul></ul><p><a class="external" href="https://github.com/ceph/ceph/pull/13197">https://github.com/ceph/ceph/pull/13197</a></p> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=852262017-01-31T12:17:28ZDavid Disseldorpddiss@suse.de
<ul></ul><p>I'd be in favour of just dropping the timeout alltogether (i.e. revert bed1a5cc05a9880b91fc9ac8d8a959efe3b3d512), as it can leave the OSD device in an unknown (mounted/unmounted) state when triggered.</p>
<p>In addition to 0ab5b7a711ad7037ff0eb7e8281b293ddfc28a2a, the ceph-disk activate_lock should also be made granular.</p> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=852492017-01-31T13:27:34ZAlexey Sheplyakovasheplyakov@mirantis.com
<ul></ul><p>I think having no timeout at all is also bad: one wants to be notified that OSD took "too long" to start.<br />There's no universally good definition of "too long", though, so there should be a way to adjust it (and sane default).</p> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=874072017-03-09T02:58:25ZKen Dreyerkdreyer@redhat.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=879382017-03-24T07:53:46ZKefu Chaitchaikov@gmail.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=909692017-05-11T13:48:11ZAlexey Sheplyakovasheplyakov@mirantis.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Pending Backport</i></li></ul> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=909702017-05-11T13:49:37ZAlexey Sheplyakovasheplyakov@mirantis.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/19910">Backport #19910</a>: jewel: random OSDs fail to start after reboot with systemd</i> added</li></ul> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=909792017-05-11T20:42:58ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Backport</strong> set to <i>jewel</i></li></ul> Ceph - Bug #18740: random OSDs fail to start after reboot with systemdhttps://tracker.ceph.com/issues/18740?journal_id=972862017-08-22T08:00:37ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Status</strong> changed from <i>Pending Backport</i> to <i>Resolved</i></li></ul>