Bug 976741
Summary: | rhq storage node data model - record is not being removed from db and ui after uninventory | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Armine Hovsepyan <ahovsepy> |
Component: | UI | Assignee: | John Sanda <jsanda> |
Status: | CLOSED WONTFIX | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | JON 3.2 | CC: | jsanda, mfoley |
Target Milestone: | GA | ||
Target Release: | JON 3.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-28 14:49:38 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: | |||
Bug Depends On: | |||
Bug Blocks: | 951619 |
Description
Armine Hovsepyan
2013-06-21 10:48:38 UTC
This is not fully implemented yet. Removing a storage node from inventory is going to have to do several things including, * Remove the resource hierarchy from the database * Remove the storage node entity from the database * Remove the node from the Cassandra cluster The last one is the tricky part. There are JMX operations we want to invoke to let other nodes in the cluster know that we are permanently removing the node. Then depending the cluster size, we may have to change the replication factor for the cluster and perform maintenance to make sure data is where it belongs in the cluster. Per 7/1 BZ triage: target jon32 This needs to be implemented as part of the JON3.2 Beta/RHQ4.9 Support for undeployment is available with master builds. https://docs.jboss.org/author/display/RHQ/Deploying+Storage+Nodes provides the details of what is involved in the process. Moving to ON_QA. create a separate bug#1002174 closing this bug as won't fix |