ceph-deploy osd create host:/path/to/osd does not activate
When using osd create host:disk, it does prepare+activate. When you do it against host:path, though, it prepares and does not activate. Possibly because there's no hotplug event?
Suggest making it behave the same for paths & disks. Alternatively, could document the difference.
Workaround: Call osd activate after osd create (or use prepare->activate instead).
#2 Updated by Alfredo Deza over 5 years ago
- Status changed from New to 4
For some reason that is not entirely clear to me, `osd create` calls `prepare` and then does this behind the scenes:
return remoto.process.run( conn, [ 'udevadm', 'trigger', '--subsystem-match=block', '--action=add', ], )
But `activate` does something completely different! it doesn't even call `udevadm`! it uses ceph-disk:
remoto.process.run( distro.conn, [ 'ceph-disk', '-v', 'activate', '--mark-init', distro.init, '--mount', disk, ], )
I am not clear about the consequences of just not calling udevadm and going for `activate` after `prepare`