When we have an event order like vm stop and later vm delete it could happen that vm would be already removed from inventory during the first event refresh which would cause second refresh to fail during disconnect_storage step. Expected behavior: disconnect_storage is able to handle situation when a vm was already removed.
How would the bug look like from user's perspective? Do I understand correctly that the reproduction steps are these? 1. Stop VM 2. Delete VM
(In reply to Jan Zmeskal from comment #4) > How would the bug look like from user's perspective? Do I understand > correctly that the reproduction steps are these? > 1. Stop VM > 2. Delete VM Correct, the issue is that second needs to be done just after first.
I tried to verify in this manner: 1. I had RHV provider in CFME 2. I added one running VM (from within RHV) and refreshed relationships in CFME 3. VM is visible in CFME inventory 4. I powered off VM from CFME 5. Right after that I clicked "Remove selected items from inventory" for the given VM 6. Observing logs (see attachment) -> no error found 7. Refreshed relationships in CFME 8. VM is still visible in CFME inventory under RHV provider 9. I tried removing VM again 10. Refreshed relationships for the provider 11. VM is still visible I believe this is not what is supposed to be happening, is that right? As far as I understand it, the VM should have been removed from inventory in this scenario. Please correct me if I am wrong.
Created attachment 1352576 [details] evm.log when trying to verify
The steps are not correct. Your step 5 is not correct. You want to retire a vm not remove it from inventory. Retire means that it will be removed from ovirt and remove from inventory means that on next refresh it will be recreated.
(In reply to Piotr Kliczewski from comment #8) > The steps are not correct. Your step 5 is not correct. You want to retire a > vm not remove it from inventory. Retire means that it will be removed from > ovirt and remove from inventory means that on next refresh it will be > recreated. I repaired my steps and after powering off the VM, I retired it. Everything worked as expected and no error found in evm.log.