On Tue, Jan 29, 2019 at 5:50 PM Ryan Harper <1812...@bugs.launchpad.net> wrote:
> I'm not 100% sure at which point ceph/charms make use of the dname > symlinks, but ceph appears to be up much earlier than this. > > $ journalctl -o short-monotonic -D fd6c366f929d47a195590b3c6dc9df5a -u > ceph* > -- Logs begin at Tue 2019-01-29 14:20:56 UTC, end at Tue 2019-01-29 > 15:23:10 UTC. -- > [ 290.386737] ln-sv-ostk01 systemd[1]: Reached target ceph target > allowing to start/stop all ceph*@.service instances at once. > [ 307.411830] ln-sv-ostk01 systemd[1]: Reached target ceph target > allowing to start/stop all ceph-radosgw@.service instances at once. > [ 308.321612] ln-sv-ostk01 systemd[1]: Reached target ceph target > allowing to start/stop all ceph-osd@.service instances at once. > [ 309.064386] ln-sv-ostk01 systemd[1]: Reached target ceph target > allowing to start/stop all ceph-mon@.service instances at once. > [ 309.911307] ln-sv-ostk01 systemd[1]: Reached target ceph target > allowing to start/stop all ceph-mgr@.service instances at once. > > Those are the top level target systemd configurations that get enabled and started on package install so I think they can be ignored in the context of this bug. A ceph-osd@<UUID> is an actual OSD starting associated with a specific block device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812925 Title: No OSDs has been initialized in random unit with "No block devices detected using current configuration" To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/1812925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
