** Changed in: ceph (Ubuntu Zesty)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Zesty)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A quick test to introduce the ceph-mon target indicates that this looks
OK from a systemd perspective.
** Summary changed:
- Ceph mon and osd don't restart on reboot with Xenial
+ Ceph mon and osd don't restart on reboot with Xenial when using
ceph-{mon,osd}@ systemd units
--
You received
I'll do some testing around running with targets and units of the same
name to ensure we don't regress tools which use the older, debian
provided systemd units; if that works OK for zesty, we can SRU the
target file updates back to xenial as well.
** Also affects: ceph (Ubuntu Yakkety)
OK so making the assumption that the ceph-ansible tooling relies on the
ceph-mon@ units, I can confirm that a ceph-mon process is not
automatically started on reboot.
This is a bit of a misalignment between ceph provided packaging and
what's in ubuntu and debian (due to historical introduction of
OK did a quick sanity check using charm; the ceph-mon daemon is managed
using the distro provided ceph-mon systemd unit (not the upstream
provided ceph-mon@ systemd unit); ceph-osd are managed in the standard
way and do restart OK on reboot - specification I think the udev events
that happen on
I switch a ceph-mon unit over to use the ceph-mon@ unit instead; looks
like that won't work well:
Created symlink from /etc/systemd/system/ceph-mon.target.wants/ceph-mon
@juju-0f0ab8-ceph-testing-0.service to /lib/systemd/system/ceph-
mon@.service.
as the ceph-mon target does not exist. We
Comparing upstream tip of jewel vs ubuntu:
install -m0644 systemd/ceph.target debian/ceph-
common/lib/systemd/system
install -m0644 systemd/ceph-mon.target
debian/ceph-mon/lib/systemd/system
install -m0644 systemd/ceph-osd.target
debian/ceph-osd/lib/systemd/system
I agree that there is a behavioural difference between the systemd
configurations provided by upstream, and the systemd configuration in
distro (and the reason why is outlined in bug 1627640).
Services not restarting post reboot is not something I've seen
(deploying using charms which don't do
I will add that Ceph Ansible v2.0.0 was used to install Ceph from both
the distro apt repo and UCA, both with the same result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646583
Title:
Ceph mon
