Bug 1288198

Summary:	calamari reports defunct clusters even after explicitly deleting them from the API
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Christina Meno <gmeno>
Component:	Calamari	Assignee:	Christina Meno <gmeno>
Calamari sub component:	Back-end	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	low
Priority:	low	CC:	anharris, ceph-eng-bugs, cjanisze, flucifre, kdreyer, mhackett
Version:	1.3.1
Target Milestone:	rc
Target Release:	1.3.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-20 20:49:08 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:
Embargoed:

Description Christina Meno 2015-12-03 19:29:38 UTC

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: