Bug 1288198 - calamari reports defunct clusters even after explicitly deleting them from the API
calamari reports defunct clusters even after explicitly deleting them from th...
Status: NEW
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Calamari (Show other bugs)
1.3.1
Unspecified Unspecified
low Severity low
: rc
: 1.3.4
Assigned To: Gregory Meno
ceph-qe-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-03 14:29 EST by Gregory Meno
Modified: 2017-10-17 11:20 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gregory Meno 2015-12-03 14:29:38 EST
Description of problem:

we are reusing messed up CEPH deployment. Customer wanted to destroy old one 1.2.X and build a new one on the same hardware 1.3 ... we have done it and the new ceph cluster is showing up in calamari properly, but also there is a drop down menu on top right hard corner that shows the old messed up cluster that doesn't exist anymore

sudo salt '*' ceph.get_heartbeats reports only the new cluster FSID


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


How reproducible:


Steps to Reproduce:
1. bring up a ceph cluster and attach it to calamari
2. destroy that cluster
3. build a second cluster using the same hosts
4. connect it to calamari
5. attempt to delete the first cluster


Actual results:

GET /api/v2/cluster reports two clusters

Expected results:

GET /api/v2/cluster reports just the new cluster


Additional info:

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