Bug 1312581

Summary: [DOC]:- Old /var/lock/subsys/diamond lock file needs to be deleted inorder to start diamond services after upgrading RHEL6.6 ceph 1.2.3------> RHEL7.2 ceph 1.3.2
Product: Red Hat Ceph Storage Reporter: shylesh <shmohan>
Component: DocumentationAssignee: Bara Ancincova <bancinco>
Status: CLOSED CURRENTRELEASE QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.3.2CC: gmeno, hnallurv, kdreyer, ngoswami
Target Milestone: rc   
Target Release: 1.3.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-19 17:20:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description shylesh 2016-02-27 15:25:55 UTC
Description of problem:

After upgrading from RHEL6.6 ceph 1.2.3 to RHEL 7.2 and ceph from 1.2.3 to 1.3.2 diamond service might fail to start. so check whether old /var/lock/subsys/diamond lock file exists on the corresponding node and delete the lock file and restart the diamond service in order to get the calamari host graphs.

This needs to be documented .

Comment 5 Christina Meno 2016-03-11 19:34:51 UTC
Bara,

This step should happen on the cluster nodes connected to calamari.

It would be great to have in right here and the next step.

" On nodes that were previously connected to Calamari and that you identified in step 7, perform the following steps:

    Remove the old salt-master public key: and that you identified in step 7

    # rm /etc/salt/pki/minion/minion_master.pub"

Comment 7 shylesh 2016-03-23 09:19:44 UTC
Now doc has below mentioned info , hence marking it as verified 

Check if the old /var/lock/subsys/diamond lock file exists and if so, delete the file and restart the diamond service:

# rm /var/lock/subsys/diamond
# systemctl restart diamond.service