Bug 536247 (RHQ-618)
Summary: | RFE: resource *delete* should also remove (uninventory) logically related resources | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Charles Crouch <ccrouch> |
Component: | Inventory | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 1.0 | CC: | bkramer, dasimmon, jochen.riedlinger, jshaughn, kejohnso, loleary |
Target Milestone: | --- | Keywords: | FutureFeature, Improvement |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://jira.rhq-project.org/browse/RHQ-618 | ||
Whiteboard: | |||
Fixed In Version: | 1.4 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Charles Crouch
2008-06-23 22:01:00 UTC
this could/would be fixed by implementing the relationship service. This bug was previously known as http://jira.rhq-project.org/browse/RHQ-618 This bug is related to RHQ-372 This bug incorporates RHQ-323 This is not only true for a deletion of an EAR, but also for an uninventory of that EAR. Also not only the SLSBs(EJB-JARs) is still there, but all other embedded elements of that EAR (RAR, WAR, ) We deploy our EARs with names like e.g.: OurApp-2.2.4.ear (with embedded OurApp-EJB-2.2.4.jar, OurApp-web-2.2.4.war) and want to uninventory them when updating to OurApp-2.2.5.ear It is too much work not just to uninventory the EARs but also all children..... needinfo ccrouch: latest thoughts? I have raised the following https://bugzilla.redhat.com/show_bug.cgi?id=670749 before I found this one. If you check the steps to reproduce in 670749 you will see exactly the same test scenario. *** Bug 670749 has been marked as a duplicate of this bug. *** Although not a silver bullet, there is some ability for the work in Bug 1093822 to potentially have a positive impact here. |