Hide Forgot
Created attachment 1141235 [details] 5.5.3.2 Description of problem: The VM after retirement is deleted and no longer exists. After relation refresh the VM won't apper. Version-Release number of selected component (if applicable): 5.5.3.2 How reproducible: 100% Steps to Reproduce: 1. Choose any VM 2. Go to Lifecycle -> Retire VM now 3. Refresh page and wait Actual results: VM no longer exists, take a look at screen shot. Expected results: The VM shouldn't be deleted and the status of VM is Retired. This behavior is on 5.5.2.4, take a look on the another screen shot. Additional info:
Created attachment 1141236 [details] 5.5.2.4
The latest default infrastructure retirement state-machine removes the VM from the provider. There is also an "Unregister" state-machine provided which will remove the VM from the provider but not delete the backing files. The state-machine configuration can be overridden to match the user's requirements by either commenting out the states they do not want to run (RemoveFromProvider/CheckRemovedFromProvider/DeleteFromVMDB) or replacing them with different methods.
Hi Greg, If now it's gonna be default behavior available out of the box, the BZ could be close as NOTABUG. Thanks, -Taras
It is the default behavior to remove the VM from the provider during retirement.