Bug 1324578 - Power state "suspended" of the terminated EC2 instance
Summary: Power state "suspended" of the terminated EC2 instance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Marcel Hild
QA Contact: Pavol Kotvan
URL:
Whiteboard: ec2
Depends On:
Blocks: 1327726
TreeView+ depends on / blocked
 
Reported: 2016-04-06 17:07 UTC by Pavol Kotvan
Modified: 2016-11-29 10:03 UTC (History)
4 users (show)

Fixed In Version: 5.6.0.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1327726 (view as bug list)
Environment:
Last Closed: 2016-06-29 15:47:46 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Comment 2 Greg Blomquist 2016-04-07 14:09:20 UTC 
Marcel, this sounds like a dup possibly.  Can you validate that?
Comment 3 Marcel Hild 2016-04-07 15:11:23 UTC 
When terminating an instance, we are setting the state to pending, which means suspended here:
https://github.com/ManageIQ/manageiq/blob/master/gems/manageiq-providers-amazon/app/models/manageiq/providers/amazon/cloud_manager/vm/operations.rb#L8

I would change that to "shutting-down", which is what it actually does.
Would this solve this?

Greg and Pavol, I'm not sure about the terminology about "archived" here. But from my understanding it makes sense to move terminated instances straight to the archived state.
Comment 4 Marcel Hild 2016-04-13 21:25:49 UTC 
fixed upstream https://github.com/ManageIQ/manageiq/pull/7926
should we backport this to 5.5.z?
Comment 5 Dave Johnson 2016-04-15 16:03:14 UTC 
Marcel, we should backport, yes please.
Comment 10 errata-xmlrpc 2016-06-29 15:47:46 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
Note You need to log in before you can comment on or make changes to this bug.