Description of problem: When there is a resource upgrade conflict, the only way to resolve that situation is to remove all but one of the conflicting resources and restart the plugin container on given machine. To be able to restart the plugin container, the user has to either have a command line access to that agent (which is not very common) or have that agent inventoried (which they don't have to). A worse situation is if the agent resource itself failed upgrade and therefore is stopped and unable to invoke operations. Adding the required ops to the platform resource (along with the already existing operation to run the discovery on that platform) would resolve all those situations, because the user would always be able to restart the plugin container for that platform. Version-Release number of selected component (if applicable): 4.1.0-SNAPSHOT