Bug 1322015

Summary: Power state "off" of the terminated EC2 instance
Product: Red Hat CloudForms Management Engine Reporter: Taras Lehinevych <tlehinev>
Component: ProvidersAssignee: Marcel Hild <mhild>
Status: CLOSED ERRATA QA Contact: Taras Lehinevych <tlehinev>
Severity: high Docs Contact:
Priority: high    
Version: 5.5.0CC: cpelland, dajohnso, hkataria, jfrey, jhardy, mfeifer, mpovolny, obarenbo, tlehinev
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ec2:power
Fixed In Version: 5.6.0.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1322885 (view as bug list) Environment:
Last Closed: 2016-06-29 15:45:41 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1310067, 1322885    

Description Taras Lehinevych 2016-03-29 14:51:44 UTC 
Description of problem:
Currently when you terminate the ec2 instance the power state will be off.
More information https://github.com/ManageIQ/manageiq/issues/6955

Version-Release number of selected component (if applicable):
5.5

How reproducible:
100%

Steps to Reproduce:
1. Go to EC2 instance
2. Terminate it
3. Wait and check power state

Actual results:
The power state is off

Expected results:
The power state should be terminated

Additional info:
This issue discussed on github
https://github.com/ManageIQ/manageiq/issues/6955
and PR
https://github.com/ManageIQ/manageiq/pull/7477
Comment 2 Dave Johnson 2016-03-31 00:46:06 UTC 
This might be a config option on EC2 itself where you state the behavior of terminate.
Comment 3 Marcel Hild 2016-04-05 13:39:42 UTC 
merged upstream
Comment 4 Taras Lehinevych 2016-04-19 11:33:10 UTC 
Verified in 5.6.0.1-beta2
Comment 6 errata-xmlrpc 2016-06-29 15:45:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1348