udevadm info -e >/tmp/1828617-2.out
~# ls -l /var/lib/ceph/osd/ceph*
-rw--- 1 ceph ceph 69 May 21 08:44
/var/lib/ceph/osd/ceph.client.osd-upgrade.keyring
/var/lib/ceph/osd/ceph-11:
total 24
lrwxrwxrwx 1 ceph ceph 93 May 28 22:12 block ->
/dev/ceph-33de740d-bd8c-4b47-a601-3e6e634e489a/osd-b
journalctl --no-pager -lu systemd-udevd.service >/tmp/1828617-1.out
Hostname obfusticated
lsblk:
NAME
MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0
Charm is cs:ceph-osd-284
Ceph version is 12.2.11-0ubuntu0.18.04.2
The udev rules are created by curtin during the maas install.
Here's an example udev rule:
cat bcache4.rules
# Written by curtin
SUBSYSTEM=="block", ACTION=="add|change",
ENV{CACHED_UUID}=="7b0e872b-ac78-4c4e-af18-8ccdce5962f6",
Just one update, if I change the perms of the symlink made (chown -h)
the OSD will actually start.
After rebooting, however, I found that the links I had made had gone
again and the whole process needed repeating in order to start the OSD.
--
You received this bug notification because you are a
Added field-critical, there's a cloud deploy ongoing where I currently
can't reboot any hosts, nor get some of the OSDs back from a host I
rebooted, until we have a workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
I'm seeing this in a slightly different manner, on Bionic/Queens.
We have LVMs encrypted (thanks Vault), and rebooting a host results in
at least one OSD not returning fairly consistently. The LVs appear in
the list, however the difference between a working and a non-working OSD
is the lack of li
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1828617
Title:
Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
Stat
Thanks! I won't claim to understand what that change did, but adding
the two lines as requested does seem to resolve the issue. I opened up
Netflix and was able to watch, without the crash, and there wasn't any
new entries in syslog.
--
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 1387251 ***
https://bugs.launchpad.net/bugs/1387251
** This bug has been marked a duplicate of bug 1387251
apparmor conflict with precise cloud archive
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
9 matches
Mail list logo