Bug 535536 (RHQ-2220) - Resource count in group wrong after deletion of a service in it
Summary: Resource count in group wrong after deletion of a service in it
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: RHQ-2220
Product: RHQ Project
Classification: Other
Component: Inventory
Version: 1.2
Hardware: All
OS: All
high
medium
Target Milestone: GA
: RHQ 4.12
Assignee: RHQ Project Maintainer
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks: rhq_triage
TreeView+ depends on / blocked
 
Reported: 2009-07-07 19:52 UTC by Heiko W. Rupp
Modified: 2014-12-15 11:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
2.2.0.GA on RHEL 5.3
Last Closed: 2014-12-15 11:36:28 UTC
Embargoed:

Attachments (Terms of Use)

Description Heiko W. Rupp 2009-07-07 19:52:00 UTC 
THis is related to RHQ-2219 and already described in it

I created as rhqadmin a classic compatible group with 9 war files (services), then deleted one war file from inventory, 
went back to the group hub ( still showed 9 resources for the group, all up). 
Also refreshing the hub does not decrease the number of war files in the group or have the deleted
one appear in red.

Unfortunately accessing the group inventory is not possible du to RHQ-2219 to see how it looks like.
Comment 1 Red Hat Bugzilla 2009-11-10 21:00:15 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2220
This bug relates to RHQ-2219
Comment 2 wes hayutin 2010-02-16 16:55:10 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 3 wes hayutin 2010-02-16 17:00:25 UTC 
making sure we're not missing any bugs in rhq_triage
Comment 4 Jay Shaughnessy 2014-05-05 22:23:48 UTC 
This is likely fixed. Asking for test.
Comment 5 Heiko W. Rupp 2014-12-15 11:36:28 UTC 
Bulk close of items fixed in RHQ 4.12

If you think this is not solved, then please open a *new* BZ and link to this one.
Note You need to log in before you can comment on or make changes to this bug.