Description of problem: Retiring a aws instance fails to update the instance's power state once it has fully powered off. Last long message concerning power state shows [----] I, [2015-08-14T14:39:45.215222 #3969:afbea0] INFO -- : <AutomationEngine> <AEMethod [/ManageIQ/Cloud/VM/Retirement/StateMachines/Methods/amazon_ check_pre_retirement]> Starting [----] I, [2015-08-14T14:39:45.547303 #3969:8b18de0] INFO -- : <AutomationEngine> <AEMethod amazon_check_pre_retirement> Instance:<last-test> on EMS:<g ss-aws has Power State:<powering_down> [----] I, [2015-08-14T14:39:45.559813 #3969:afbea0] INFO -- : <AutomationEngine> <AEMethod [/ManageIQ/Cloud/VM/Retirement/StateMachines/Methods/amazon_ check_pre_retirement]> Ending AWS Console shows the instance as being stopped. CloudForms UI stays in the powering_down Version-Release number of selected component (if applicable): 5.4.1 How reproducible: very Steps to Reproduce: 1. retire a aws instance with cfme 2. 3. Actual results: Expected results: Additional info:
Please send steps to reproduce. We normalize the power states across cloud providers so we might not match 1-1 with EC2. The retirement takes a while and depends on if it is a EBS instance or a regular instance. They take different paths according to Amazon http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-lifecycle.html#lifecycle-differences
Any updates on this ticket, can we close it
Hi, The power state shows powering_down until the next major ems refresh occurs for aws. The instance displayed that it was powered off in the aws console within seconds of the retirement state machine executing. It seems like we need to perform a ems refresh at the very end of the retirement state machine for amazon instead of leaving it in the "powering down" mode. Users will have to wait until the next generic timed refresh to occur or manually kick off a refresh just to have correct power state information. This is pretty easy to see by monitoring both the aws console and retiring a given aws instance.
Can't recreate this. Could they be using the old retirement state machine
Madhu, I think this bz was due to aws config not configured correctly. Going to close the bz.