Bug 1295920

Summary: Amazon Instance Power State Inconsistency
Product: Red Hat CloudForms Management Engine Reporter: Lester Claudio <claudiol>
Component: ProvidersAssignee: Joe Vlcek <jvlcek>
Status: CLOSED NOTABUG QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.5.0CC: jfrey, jhardy, jvlcek, obarenbo
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-12 14:21:48 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:
Attachments:
Description Flags
CFME Appliance Screen Shot - CFME 4.0
none
AWS Console Screen Shot none

Description Lester Claudio 2016-01-05 19:21:27 UTC
Created attachment 1111927 [details]
CFME Appliance Screen Shot - CFME 4.0

Description of problem:
On the CFME Appliance the power state for the instance show as powering_up when the instance power state in AWS is running.


Version-Release number of selected component (if applicable):
Session Information
Server Name EVM
Version: 5.5.0.13.20151201120956_653c0d4

How reproducible:
Always. 

Steps to Reproduce:
1. Select Cloud > Instances
2. Select an instance
3. Select Power > Start

Actual results:
The instance will start powering up but the Power State will show as powering_up even though the instance is already up and running.

Expected results:
The power state should show running.

Additional info:
Added attachments to show the CFME appliance and the AWS Console.

Comment 1 Lester Claudio 2016-01-05 19:22:16 UTC
Created attachment 1111928 [details]
AWS Console Screen Shot

Comment 4 Joe Vlcek 2016-01-12 14:21:48 UTC
I investigated and noticed that doing a refresh will update the status.
The issue seems that the time laps between scheduled refreshes can cause a
delay in updating status.

I will close this as not a bug. Please reopen if more data can be provided.