Red Hat Bugzilla – Bug 1297463
ceph systemd unit file issues
Last modified: 2017-08-08 08:38:39 EDT
Created attachment 1113624 [details]
ceph systemd compatibility patch
ceph systemd unit files fails with non-default cluster name. The only supported cluster name is "ceph". We've fixed it with a complex fix:
1. created /usr/sbin/ceph-custom-daemon script to wrap primary ceph daemons and tools (ceph-mon, ceph-osd, ceph-mds, radosgw)
2. fixed ceph-disk to use cluster name and osd ID as identifier
3. fixed systemd unit files to use wrapper script instead direct call to ceph binaries
This allows to use commands like these:
systemctl enable firstname.lastname@example.org
systemctl start email@example.com
systemctl stop firstname.lastname@example.org
The patch is attached.
We built ceph-9.2.0 against CentOS version 7, but the same way can be used in Fedora.
I do not see this in upstream master (or jewel or infernalis) branch, yet. Do you have any PR for this? I do rebase fedora ceph packages regularly so as long as these changes make it/get backported into the next 9.2 release they will make their way into the next fedora build.
Created attachment 1114129 [details]
Fixes /usr/libexec/ceph/ceph-osd-prestart.sh missed in main patch
This patches is not in an upstream yet.
I don't ever guess will it be therer or not because that's a "dirty hack".
And there is one issue for all ceph users who use non-default cluster name: they will be very unhappy (exactly like me when I found that my cluster doesn't start anymore until I fix systemd unit files)
I've posted a bugfix in mainstream http://tracker.ceph.com/issues/14348
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.