Bug 1274810 - 1.3.1: 'service ceph start' on mon daemon ends with a message: /etc/init.d/ceph: line 496: ceph-disk: command not found
Summary: 1.3.1: 'service ceph start' on mon daemon ends with a message: /etc/init.d/ce...
Keywords:
Status: CLOSED DUPLICATE of bug 1225183
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Unclassified
Version: 1.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 1.3.1
Assignee: ceph-eng-bugs
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-23 14:27 UTC by Harish NV Rao
Modified: 2022-02-21 18:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-28 09:27:33 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-3294 0 None None None 2022-02-21 18:15:48 UTC

Description Harish NV Rao 2015-10-23 14:27:42 UTC
Description of problem:

 'service ceph start' on mon daemon ends with a message: /etc/init.d/ceph: line 496: ceph-disk: command not found

 mon daemon starts.

Version-Release number of selected component (if applicable): 0.94.3


How reproducible: always


Steps to Reproduce:
1. issue 'service ceph start' on a mon node

Actual results:
mon daemon start with a message : /etc/init.d/ceph: line 496: ceph-disk: command not found

Expected results:
the above mentioned message should not be displayed

Additional info:
service ceph restart does not show this message on mon node:

[cephuser@magna037 ~]$ sudo service ceph restart
=== mon.magna037 === 
=== mon.magna037 === 
Stopping Ceph mon.magna037 on magna037...kill 24685...done
=== mon.magna037 === 
Starting Ceph mon.magna037 on magna037...
Running as unit run-7903.service.
Starting ceph-create-keys on magna037...

Comment 2 Ken Dreyer (Red Hat) 2015-10-23 15:40:13 UTC
Harish, can we close this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1225183 ?

Comment 3 Harish NV Rao 2015-10-28 09:27:33 UTC
Yes, this can be closed as duplicate. I feel we need to add 1225183 to known issues section in 1.3 release notes. I will mark it accordingly.

*** This bug has been marked as a duplicate of bug 1225183 ***


Note You need to log in before you can comment on or make changes to this bug.