-
Notifications
You must be signed in to change notification settings - Fork 911
Description
Description of problem:
Starting the SmartState Analysis is not handled in consistent way across providers.
From All datastores
page
Compute -> Infrastructure -> Datastores; [Select one RHV DS from the list], [Click on Configure -> Start SSA]
The button for starting the analysis of datastore on RHV providers is enabled, but the start is not sucesfull with message: "SmartState Analysis action does not apply to selected items". On vmware provider, the SSA starts fine.
From Provider datastores page
Compute -> Infrastructure -> Providers; [Select RHV provider], [Select Datastores], [Check one DS from the list], [Click on Configure -> Start SSA]
The SSA starts on datastore of both -- vmware as well as RHV. Message ... scan successfully initiated when trying from the datastore Details page" is displayed.
From Datastore Details
page:
Compute -> Infrastructure -> Providers; [Select RHV provider], [Select Datastores from the table].
It seems no matter which navigation path is taken, The Configure
button is disabled on RHV. It is enabled on vmware and works fine.
Version-Release number of selected component (if applicable):
5.11.6.0.20200526234234_3fcafeb
5.11.7.0.20200714215453_0da8a4
How reproducible:
1/1 For each CFME version noted.
It is important to note that when vmware provider is deleted, some items are archived, which can manifest as duplicated items (datastores for example) and that may cause a confusion.
Steps to Reproduce:
- Add a RHV and vmware provider
- Go to datastore trough provider and select it or select some DS from the All datastores page or display Details page of the datastore
- Click on button for starting SSA
Actual results:
When not going trough the provider, SSA is not allowed:
SmartState Analysis action does not apply to selected items
is displayed
Expected results:
Hard to tell what should be expected. The compatibility matrix is not really populated for RHV in the documentation. The behaviour is not consistent even for single CFME version and single provider.