Red Hat Bugzilla – Bug 535973
Uninventory button should not be displayed for Services
Last modified: 2014-11-09 17:49:54 EST
If a Service is uninventoried, it will be rediscovered on the next Service scan and auto-imported by the Server. The auto-import of Services is by design, but it has the side effect of making uninventorying Services rather pointless. So it would be less confusing for users to not even provide the option to uninventory Services. On the Browse Resources page, this would mean not displaying an Uninventory button when viewing Services. On the Inventory tab's Child Resources section, it would mean not displaying the Uninventory button if all child Resources are Services. In the case where there is a mix of Server and Service child Resources, the button would have to be shown for the sake of the Servers.
What happens now if they uninventory a service? Does it get uninventoried successfully and then silently appear on the next discovery?
If that's the case, I'd argue this should be higher than a minor bug. I think it's going to be confusing and frustrating to the user if we give them the ability to uninventory a service and then repeatedly ignore their wishes by re-adding it on each discovery.
I rather think we should have an "uninventory and ignore" button, that uninventories the service and leaves it as ignored in the resource tree, so that it won't get autodiscovered.
On my Mac I have 4 network interfaces, of which at least one is always administratively down. I want to get rid of this in the inventory and not having it showing red in half of the application.
on the one hand, "uninventory and ignore" makes sense; on the other hand, the system today does not allow ignoring services yet. this still needs more discussion.
rev2438 - suppress univentory button for services, since they get automatically rediscovered;
Verified, rev2522. no "uninventory" button for services. Still there for platforms and servers.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-372
This bug is related to RHQ-910
This bug relates to RHQ-618