Bug 1084650

Summary:	Add better support for handling unmanaged storage nodes
Product:	[JBoss] JBoss Operations Network	Reporter:	John Sanda <jsanda>
Component:	Core Server, Storage Node	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	hrupp, mfoley
Target Milestone:	---
Target Release:	JON 4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1084649	Environment:
Last Closed:	2019-06-24 15:05:58 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:	1084649
Bug Blocks:

Description John Sanda 2014-04-05 01:58:26 UTC

+++ This bug was initially created as a clone of Bug #1084649 +++

Description of problem:
An unmanaged storage node is (or was) part of the cluster, has a StorageNode entity in the database, but does not have an associated Resource entity. This could easily happen as a result of a user removing the storage node resource from inventory. The undeploy process does not work in this situation. The user would either have to re-import the storage node resource back into inventory or perform the steps manually. The undeploy process needs to handle this situation where we cannot run the decommission operation, which is supposed to be run on the node being removed from the cluster. The StorageServiceMBean.removeNode(String id) will need to be used in this situation to force the removal of the node from the cluster. 

This forced removal will also be applicable to situations where the node is down indefinitely. This might occur if the user improperly removes the storage node from the cluster by shutting it down, removing it from inventory, and then purging the bits from disk.

Handling of unmanaged nodes should also affect our topology change detection. For instance, suppose a user installs multiple nodes prior to server installation. This requires manual configuration in order for them to cluster properly. If the user does not run the agent along side one of those nodes, then it won't get discovered and imported into inventory. We need to detect and handle this.

We also need to handle the case where the user manually decommissions the node, and the resource is still in inventory. When this happens, we need to automatically finish the undeploy process. And if we have a StorageNode entity with no associated Resource entity and then detect that the node is manually decommissioned, we need to finish the undeploy process in this case as well.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 John Sanda 2014-08-29 12:27:26 UTC

Bumping the target release due to time constraints. Work has been started
though in the storage_workflow branch.

Comment 3 Filip Brychta 2019-06-24 15:05:58 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.