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*
> --
Workaround for the time being until the actual root cause is identified:
juju run --application ceph-osd "sudo udevadm trigger --subsystem-
match=block --action=add"
before unsealing and authorising the vault charm. Charm task marked
incomplete pending diagnosis of what's actually mangling the
** Changed in: charm-ceph-osd
Importance: Critical => High
** Changed in: charm-ceph-osd
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/181
Re-triggering udev outside of the charm creates the missing by-dname
entries:
sudo udevadm trigger --subsystem-match=block --action=add
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs
Raising a bug task for bcache-tools
** Also affects: bcache-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1812925
Title:
An obvious workaround would be to trigger a re-scan before the ceph-osd
charm tries to osdize the bcache devices - I would consider this a
workaround only as the by-dname devices really should be present before
the charm executes.
--
You received this bug notification because you are a member of
