Description of problem: 30 mins after the removal of a rhev provider the datastores are still displayed in the UI but when a attempting to delete them using the ui the following error message is displayed "Datastores no longer exists" Version-Release number of selected component (if applicable): 5.8.0.9-alpha2.20170404195944_1d7ece4 How reproducible: Steps to Reproduce: 1. Delete a Rhev provider 2. allow time for all objects to be deleted hosts etc 3. Attempt to delete the leftover datastores. Actual results: Expected results: Additional info: [----] I, [2017-04-05T15:48:34.786361 #15459:e665a4] INFO -- : MIQ(MiqExpression.build_relats) Building relationship tree for: [ => CimLogicalDisk]... [----] I, [2017-04-05T15:48:34.787633 #15459:e665a4] INFO -- : MIQ(MiqExpression.build_relats) Building relationship tree for: [ => SniaFileShare]... [----] E, [2017-04-05T15:48:45.641444 #15459:e665a4] ERROR -- : MIQ(storage_controller-x_button): Datastores no longer exists [----] W, [2017-04-05T16:01:19.112147 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): Session object size of 108.8 KB exceeds threshold of 100 KB [----] W, [2017-04-05T16:01:19.112477 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): _csrf_token <String> Size 44 [----] W, [2017-04-05T16:01:19.112630 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): adv_search <Hash> Size 895 Elements 1 [----] W, [2017-04-05T16:01:19.112739 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): assigned_filters <Hash> Size 4 Elements 0 [----] W, [2017-04-05T16:01:19.112797 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): automation_manager_lastaction <String> Size 9 [----] W, [2017-04-05T16:01:19.112855 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): breadcrumbs <Array> Size 4 Elements 0 [----] W, [2017-04-05T16:01:19.112933 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): browser <Hash> Size 111 Elements 5 [----] W, [2017-04-05T16:01:19.112999 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): changed <FalseClass> Size 3 [----] W, [2017-04-05T16:01:19.113071 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): css <Hash> Size 297 Elements 13 [----] W, [2017-04-05T16:01:19.113135 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): customer_name <String> Size 10 [----] W, [2017-04-05T16:01:19.115480 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): edit <Hash> Size 73358 Elements 3 [----] W, [2017-04-05T16:01:19.119021 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): current <VMDB::Config> Size 40665 [----] W, [2017-04-05T16:01:19.119106 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): key <String> Size 36 [----] W, [2017-04-05T16:01:19.120320 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): new <Hash> Size 40612 Elements 41 [----] W, [2017-04-05T16:01:19.121554 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): api <Hash> Size 74 Elements 2 [----] W, [2017-04-05T16:01:19.121629 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): authentication <Hash> Size 269 Elements 15 [----] W, [2017-04-05T16:01:19.121751 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): broker_notify_properties <Hash> Size 1006 Elements 1 [----] W, [2017-04-05T16:01:19.121846 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): capacity <Hash> Size 444 Elements 2 [----] W, [2017-04-05T16:01:19.121915 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): container_scanning <Hash> Size 26 Elements 1 [----] W, [2017-04-05T16:01:19.121969 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): coresident_miqproxy <Hash> Size 103 Elements 5 [----] W, [2017-04-05T16:01:19.122049 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): database <Hash> Size 250 Elements 2 [----] W, [2017-04-05T16:01:19.122114 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): drift_states <Hash> Size 73 Elements 1 [----] W, [2017-04-05T16:01:19.122220 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): ems <Hash> Size 1130 Elements 6 [----] W, [2017-04-05T16:01:19.122347 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): ems_refresh <Hash> Size 766 Elements 18 [----] W, [2017-04-05T16:01:19.122912 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): event_handling <Hash> Size 23470 Elements 3 [----] W, [2017-04-05T16:01:19.123515 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): bottleneck_event_groups <Hash> Size 136 Elements 2 [----] W, [2017-04-05T16:01:19.124035 #15459:e665a4] WARN -- : MIQ(ops_controller-tree_select): event_groups <Hash> Size 21918 Elements 13
This issue is caused by manageiq-ui-classic "All Datastores" view where we can select a datastore and delete it. There is no check whether the datastore can be removed (relationships to vms or hosts) and "Remove Datastores" is always enabled which when clicked leads to described above issue. Whereas in in "Datastore" view button is correctly disabled when there are relationships. Based on above findings this issue looks to be generic and not RHV related.
Verified on: CFME 5.9.0.4 RHV 4.1.7.4 Verification steps: 1. Add RHV provider with some VMs, hosts and storage domains 2. Remove RHV provider and leftover VMs and hosts 3. Try to remove leftover datastores During the first step, datastores with 0 VMs and 0 hosts can indeed be removed, which is expected behaviour. However, during this verification step it was discovered that some datastores still register hosts, even though they have been removed. New bug was opened for this: https://bugzilla.redhat.com/show_bug.cgi?id=1508910