Description of problem: InventoryStatus.DELETED causes issues (ie Bug 1077668) and is completely useless. Uninventory: when user decides to uninventory a resource, for Server (and agent) it means, it has to be deleted with all it's children from the inventory (DB on server, and memory on agent) - this is correct and expected. Delete: when user Deletes a resource (parent resource has to support add/delete child facet), right now, server marks such resource as Deleted - this effectively hides resource from UI and hopefully all RemoteAPI and Rest API calls. All child resources of deleted resource are uninventoried. When (same as in case of Bug 1077668) a resource with thesame parent, resourceKey and resource type is discovered in future, the deleted one is resurrected. As one can see .. resurrecting just the deleted resources makes no sense - if we ever want to metrics/configurations etc to survive resource removal, we'd have to write it for all removed (hence including Uninventoried) resources. 1. to be able to restore Version-Release number of selected component (if applicable): JON 3.3.0 How reproducible: always Steps to Reproduce: see Bug 1077668
in master https://github.com/rhq-project/rhq/commit/8b96079f2ac4cd3ec8c7cd1c59b245e3a6a63296 this BZ depends on Bug 1077668 just moved to 3.4 also moving to 3.4
One more commit to fix ora dbupgrade issue branch: master link: https://github.com/rhq-project/rhq/commit/27057d669 time: 2015-06-12 14:19:30 +0200 commit: 27057d66909896b0394db7bb715dab8b14c32ed0 author: Libor Zoubek - lzoubek message: Bug 1168890 - Remove InventoryStatus.DELETED resource state Fix db-upgrade: correctly drop column constraints
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions