Project

General

Profile

Bug #18762

OSDs stuck using previous version Upstart script until all have been restarted

Added by Brian Andrus about 3 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
documentation
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

After a Hammer -> Jewel upgrade, OSD daemons will not start. The upstart logs show:

/proc/self/fd/9: 8: /proc/self/fd/9: /usr/libexec/ceph/ceph-osd-prestart.sh: not found

The correct Jewel init script seems to be in place:

$ sudo grep prestart /etc/init/ceph-osd.conf
/usr/lib/ceph/ceph-osd-prestart.sh --cluster="${cluster:-ceph}" -i "$id"

However it would seem that open FDs are ensuring the Hammer-era init script is used which references the incorrect location for ceph-osd-prestart.sh. This forces us to upgrade a node at a time which is more destructive than we'd like to be.

It should be noted that changes like this affect upgrade plans, and perhaps noted in documentation that single OSD rolling restarts are not possible if upstart changes are pushed.

History

#1 Updated by Brian Andrus about 3 years ago

  • Subject changed from OSDs stuck using old Upstart script until all have been restarted to OSDs stuck using previous version Upstart script until all have been restarted

#2 Updated by Shinobu Kinjo about 3 years ago

  • Category set to documentation

Also available in: Atom PDF