Created attachment 1115183 [details]
Description of problem:
The retired vm on openstack cloud provider could be running again. According to the definition CFME will not allow a retired VM to start/power on, however you can do it now.
Please take a look at screenshot, the power state on appear after resuming the vm and cfme won't shut/power off this vm.
Also, I'll attach emv and automation log files.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up OpenStack cloud provider
2. Open any virtual machine
3. Press Lifecycle -> Retire this VM
4. Wait a little bit and check the status of vm is Retired and power state suspend.
5. Go to openstack and resume this vm
6. Wait a little bit again and check the status of vm
The status of vm is Retired but power state is on. CFME allow to start/power on retired vm
The power state of vm should be off, CFME shoul shutdown/stop the vm
Also please pay attention that now the retired vm has suspend power state but maybe it will be better to terminate (not suspend) vm during retirement, in this case the customer won't be allow to start vm again.
Moreover on the screenshot you can see the time of change power state, what can be useful during log analysis.
IP is 10.16.5.163
The vm name is singleheat-server-y7aisp7ki4rs
Created attachment 1115184 [details]
Created attachment 1115185 [details]
We want close as NOT A BUG, because;
1. The statemachine workflow that runs retirement is their for the user to decide what state the VM ends up in, choices are infinite but example would be;
a) Delete from disk
b) remove from provider inventory
c) just leave on provider, but stopped or suspended.
Basically the end result is your choice.
If you wish to stop a user starting a VM using external tooling then our course of action would be to write a control policy that watches the provider for vm start events and stop them if the vm is marked as retired in CF.
this again would be your choice.
Thank you for provided information.
I'm closing this bug.
Providing doc-text since it's a known issue. Also including the doc-text in the CloudForms Management Engine 4.0 Release Notes under Known Issues, as requested in Bug 1301560.