Bug 571882 - Add ability to reference a resource's grand-child when creating a new group
Add ability to reference a resource's grand-child when creating a new group
Status: CLOSED CURRENTRELEASE
Product: RHQ Project
Classification: Other
Component: Resource Grouping (Show other bugs)
1.3
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
John Sefler
:
Depends On:
Blocks: 578348
  Show dependency treegraph
 
Reported: 2010-03-09 14:18 EST by Mark Burchard
Modified: 2014-05-27 19:31 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-05-27 19:31:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mark Burchard 2010-03-09 14:18:38 EST
Description of problem:

Customer would like to have the ability to reference a resource's grand-child when creating a new group.  Current logic only allows you to go one level deep in that direction.


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

JON 2.x


How reproducible:

Try to create a mixed group of all platforms running X application 


Steps to Reproduce:

Here are some examples we tried before concluding that this would require a code fix:

----------
resource.type.name = Web Application (WAR)
groupby resource.grandparent.name
----------

----------
resource.type.name = Web Application (WAR)
groupby resource.grandparent.name
resource.trait[Application.path].contains = sample
----------
Comment 2 Jay Shaughnessy 2014-05-27 19:31:08 EDT
"grandparent" is supported with group definitions

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