| Summary: | Retired vm is deleted on provider | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Taras Lehinevych <tlehinev> | ||||||
| Component: | Automate | Assignee: | Tina Fitzgerald <tfitzger> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Dave Johnson <dajohnso> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 5.5.0 | CC: | dajohnso, jhardy, mkanoor, nachandr, obarenbo, tfitzger, tlehinev | ||||||
| Target Milestone: | GA | ||||||||
| Target Release: | 5.6.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | retirement | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-03-29 16:33:34 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
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. |
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: