https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2014-08-12T14:11:28ZCeph Ceph-deploy - Bug #5474: ceph-deploy osd create host:/path/to/osd does not activatehttps://tracker.ceph.com/issues/5474?journal_id=393082014-08-12T14:11:28ZAlfredo Dezaadeza@redhat.com
<ul><li><strong>Assignee</strong> set to <i>Alfredo Deza</i></li></ul> Ceph-deploy - Bug #5474: ceph-deploy osd create host:/path/to/osd does not activatehttps://tracker.ceph.com/issues/5474?journal_id=394982014-08-14T09:03:19ZAlfredo Dezaadeza@redhat.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>4</i></li></ul><p>For some reason that is not entirely clear to me, `osd create` calls `prepare` and then does this behind the scenes:</p>
<pre>
return remoto.process.run(
conn,
[
'udevadm',
'trigger',
'--subsystem-match=block',
'--action=add',
],
)
</pre>
<p>But `activate` does something <strong>completely</strong> different! it doesn't even call `udevadm`! it uses ceph-disk:</p>
<pre>
remoto.process.run(
distro.conn,
[
'ceph-disk',
'-v',
'activate',
'--mark-init',
distro.init,
'--mount',
disk,
],
)
</pre>
<p>I am not clear about the consequences of just not calling udevadm and going for `activate` after `prepare`</p> Ceph-deploy - Bug #5474: ceph-deploy osd create host:/path/to/osd does not activatehttps://tracker.ceph.com/issues/5474?journal_id=424282014-10-03T09:46:45ZNeil Levinenlevine@redhat.com
<ul><li><strong>Project</strong> changed from <i>devops</i> to <i>Ceph-deploy</i></li><li><strong>Category</strong> deleted (<del><i>ceph-deploy</i></del>)</li></ul> Ceph-deploy - Bug #5474: ceph-deploy osd create host:/path/to/osd does not activatehttps://tracker.ceph.com/issues/5474?journal_id=1127772018-05-08T10:57:19ZAlfredo Dezaadeza@redhat.com
<ul><li><strong>Status</strong> changed from <i>4</i> to <i>Resolved</i></li></ul><p>No longer a problem when using ceph-volume</p>