Actions
Bug #22326
closedWhen using a custom cluster name OSDs fail to start on reboot.
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If you use a custom cluster name and reboot your OSD node that hosts OSDs created by ceph-volume they will fail to start.
This will be present in /var/log/ceph-volume.log
[2017-12-05 16:08:03,003][ceph_volume][ERROR ] exception caught by decorator Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ceph_volume/decorators.py", line 59, in newfunc return f(*a, **kw) File "/usr/lib/python2.7/site-packages/ceph_volume/main.py", line 142, in main conf.ceph = configuration.load(conf.path) File "/usr/lib/python2.7/site-packages/ceph_volume/configuration.py", line 36, in load raise exceptions.ConfigurationError(abspath=abspath) ConfigurationError: Unable to load expected Ceph config at: /etc/ceph/ceph.conf
Also, this line will show in /var/log/ceph-volume-systemd.log
stderr --> ConfigurationError: Unable to load expected Ceph config at: /etc/ceph/ceph.conf
Updated by Alfredo Deza over 6 years ago
- Status changed from New to Resolved
PR https://github.com/ceph/ceph/pull/19347
merged commit 813276e into master
Updated by Alfredo Deza over 6 years ago
Luminous backport https://github.com/ceph/ceph/pull/19530
Actions