Bug 1098187 - Resources with status down are not included in dynagroups which use resourceConfiguration in expression
Summary: Resources with status down are not included in dynagroups which use resourceC...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Configuration, Core Server, Resource Grouping
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: JON3-5
TreeView+ depends on / blocked
 
Reported: 2014-05-15 12:59 UTC by Filip Brychta
Modified: 2022-03-31 04:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1129304 0 unspecified CLOSED Newly imported resources are not included in dynagroups which use resourceConfiguration in expression for several hours 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1145732 0 unspecified NEW getLiveResourceConfiguration doesn't store resource configuration to DB 2021-02-22 00:41:40 UTC

Internal Links: 1129304 1145732

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.


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