jewel: build/ops: ceph-osd-prestart.sh fails confusingly when data directory does not exist #10812

Merged
merged 1 commit into from Oct 10, 2016

Projects

None yet

2 participants

@smithfarm smithfarm ceph-osd-prestart.sh: check existence of OSD data directory
Fixes: http://tracker.ceph.com/issues/17091
Signed-off-by: Nathan Cutler <ncutler@suse.com>
(cherry picked from commit d6ffa77)
29a8701
@smithfarm smithfarm self-assigned this Aug 22, 2016
@smithfarm smithfarm added this to the jewel milestone Aug 22, 2016
@smithfarm smithfarm added bug fix core build/ops and removed core labels Aug 22, 2016
@smithfarm smithfarm changed the title from jewel: ceph-osd-prestart.sh fails confusingly when data directory does not exist to jewel: build/ops: ceph-osd-prestart.sh fails confusingly when data directory does not exist Aug 22, 2016
@dachary
Member
dachary commented Aug 25, 2016

Hey jenkins, test this please (bluefs core dump)

@dachary
Member
dachary commented Aug 25, 2016

Hey jenkins, test this please (unrelated osd-scrub failures)

@dachary dachary changed the title from jewel: build/ops: ceph-osd-prestart.sh fails confusingly when data directory does not exist to DNM: jewel: build/ops: ceph-osd-prestart.sh fails confusingly when data directory does not exist Aug 25, 2016
@dachary
Member
dachary commented Aug 25, 2016

osd-scrub-repair.sh consistently fails

@dachary
Member
dachary commented Oct 10, 2016

jenkins test this please (no log)
and I don't see how this commit can make osd-scrub-repair.sh fail...

@smithfarm smithfarm changed the title from DNM: jewel: build/ops: ceph-osd-prestart.sh fails confusingly when data directory does not exist to jewel: build/ops: ceph-osd-prestart.sh fails confusingly when data directory does not exist Oct 10, 2016
@smithfarm
Contributor

make check bot is now happy, removing DNM

@dachary dachary merged commit 2a348d2 into ceph:jewel Oct 10, 2016

2 checks passed

Signed-off-by all commits in this PR are signed
Details
default Build finished.
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment