Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 642854

Summary: Deltacloudd 0.0.7 is not handling stopped EC2 instances properly via REST
Product: [Retired] CloudForms Cloud Engine Reporter: Jeff Johnston <jjohnstn>
Component: deltacloud-coreAssignee: Michal Fojtik <mfojtik>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: medium    
Version: 0.3.1CC: clalance, deltacloud-maint, mfojtik, rananda
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-14 15:54:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Johnston 2010-10-13 22:46:38 UTC 
Description of problem:

An EC2 instance can be stopped via the REST interface.  In the past, this used to report the EC2 instance in a TERMINATED state (0.0.5) because the instance is actually terminated when stopped.  The 0.0.7 version of deltacloudd is reporting these instances as STOPPED.  However, it is also reporting that the START action is available.  When START is issued, the state remains STOPPED and nothing happens.  The state should either change to PENDING, if a restart is actually being performed or else the START action should not be listed as available under the actions node.

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

0.0.7

How reproducible:

Create and start an EC2 instance.
Using REST, stop the instance and wait for it to become STOPPED.
Note that START is listed in actions for the instance.
Attempt to start the instance via REST.
The state will remain as STOPPED and the start action will never complete.

If a STOPPED state from a START request is supposed to indicate failure then this should be documented.

  
Actual results:


Expected results:


Additional info:
Comment 1 Chris Lalancette 2010-10-15 13:14:15 UTC 
The other option is to add back the TERMINATED state.  I'm not opposed to that, but it needs to be applied consistently across all of the drivers we have (and it was definitely *not* being done consistently before).

Chris Lalancette
Comment 2 Jeff Johnston 2010-10-15 19:30:31 UTC 
(In reply to comment #1)
> The other option is to add back the TERMINATED state.  I'm not opposed to that,
> but it needs to be applied consistently across all of the drivers we have (and
> it was definitely *not* being done consistently before).
> 
> Chris Lalancette

The tools are set up to handle this.  I think it makes sense because there is a distinct state whereby the instance can never be restarted again.  It should be documented.
Comment 3 Jeff Johnston 2010-11-18 18:51:05 UTC 
(In reply to comment #1)
> The other option is to add back the TERMINATED state.  I'm not opposed to that,
> but it needs to be applied consistently across all of the drivers we have (and
> it was definitely *not* being done consistently before).
> 
> Chris Lalancette

What is the status of this bug?  Any progress?  Does Deltacloud Tools have to put in a hack so that EC2 stopped is internally treated as TERMINATED and all actions passed back from the server are ignored?
Comment 4 Chris Lalancette 2010-11-18 19:00:33 UTC 
I haven't had any time to look at this.  Michal, is this something you might have time to look at?  The first comment lays out the problem pretty well.  The only additional thing I will add is that if we add back a TERMINATING state, we make it work consistently across all of the drivers.

Chris Lalancette
Comment 5 David Lawrence 2010-12-10 21:16:05 UTC 
Moving to Cloud Engine/Core/!.0 at the request of cpelland

Dave
Comment 6 wes hayutin 2011-06-14 15:54:38 UTC 
closing out old bugs that dev has not addressed :(
Comment 7 wes hayutin 2011-12-08 14:16:41 UTC 
perm close