Bug 1098187

Summary:	Resources with status down are not included in dynagroups which use resourceConfiguration in expression
Product:	[Other] RHQ Project	Reporter:	Filip Brychta <fbrychta>
Component:	Configuration, Core Server, Resource Grouping	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	hrupp, theute
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1069544

Description Filip Brychta 2014-05-15 12:59:43 UTC

Description of problem:
This problem is caused by a fact that resources with status down have no configuration unless you visit them directly in the UI.

This problem is visible in pre-defined dynagroup definitions for as7 plugin.

Version-Release number of selected component (if applicable):
Version :	
4.12.0-SNAPSHOT
Build Number :	
96bc0ba

How reproducible:
Always

Steps to Reproduce:
1. have a clean installation of rhq
2. register an agent which is monitoring default eap6 in domain mode
3. inventory eap6 resource
4. go to Inventory->Groups->All groups and wait for recalculation interval

Actual results:
By default eap6 in domain mode has 3 manages servers. Two are running and belong to 'main-server-group' and one is stopped which belongs to 'other-server-group'.
You can see that dynagroup named 'Managed Servers in server-group ( main-server-group )' was correctly created and contains two running managed servers. But there is no dynagroup created for the last managed server which is stopped and belongs to other server group.

Expected results:
Dynagroup named 'Managed Servers in server-group ( other-server-group )' containing the stopped managed server is created.

Additional info:
Workaround:
Navigate to the stopped managed server resource and visit a Configuration tab. Wait for recalculation. Expected dynagroup is created.

Comment 1 Libor Zoubek 2014-06-24 11:49:43 UTC

Not sure how to fix this one. In general we'd have to collect configuration for all unavailable resources, which is probably not a good idea.