Description of problem: Please add support for Datastore ID like this: scsidisk#.datastore_id = 123 The data store ID will get the precedence over the data store name. It should address a problem of Datastores with the same name, residing on different data centers, or different RHV providers, attached to CFME. There should be a way to identify the ID of the desired Datastore, in CFME database, by Datacenter/provider Version-Release number of selected component (if applicable): CFME-5.8.0.14 RHV-4.1.1.8 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This RFE is related to bug 1427498 - VM provision via restapi fail, if the chosen data store name exist more than once in CFME. It's also part of a wider problem of Datastore duplicate names in the databases, in other cases as well, like in Reports-DataStore summary, or in history Datastores which has same names as active/connected Datastores.
https://github.com/ManageIQ/manageiq-providers-ovirt/pull/37
https://github.com/ManageIQ/manageiq/pull/15101
The datastore-id aimed to solve ambiguous datastore selection, when a datastore is specified by its. A datastore name might appear more than once in one of the following scenarios: 1. The same datastore name is used by two different providers. 2. If provider was added to the ManageIQ, removed and added again - the same datastore is being kept twice. For the #1 case, when selecting a datastore by its name, the selection will be narrowed to the provider which is associated with the VM (the association is done base on the selected template). For the #2, when the provider is being removed, the associated provider ID is being deleted from the datastore entry, therefore there is no risk in ambiguous selection. Based on the above, there is no need to require specifying the datastore_id as part of the API. Implementing #1 will be done as part of solving bug 1427498.