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

Bug 871850

Summary: Stopping an instance from a stopped application gives error message : "The Instance ec2-image-1/ec2-image_4 was not stopped because Attempted to update a stale object: Instance "
Product: [Retired] CloudForms Cloud Engine Reporter: Shveta <sshveta>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1.0   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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
err none

Description Shveta 2012-10-31 14:31:46 UTC
Created attachment 636162 [details]
err

Steps to Reproduce:
1. Launched a multi-instance deployment with ec2 images
2. two instance comes up 
3. Application shows running , after some time , stop one instance
4. application shows stopped now (Red )
5. After some time stop the other instance .
This message is displayed :
"The Instance ec2-image-1/ec2-image_4 was not stopped because Attempted to update a stale object: Instance "

Instance gets stopped.
  
Actual results:


Expected results:


Additional info:

rpm -qa|grep aeolus
aeolus-configure-2.8.11-1.el6cf.noarch
aeolus-conductor-0.13.22-1.el6cf.noarch
rubygem-aeolus-cli-0.7.7-1.el6cf.noarch
aeolus-conductor-doc-0.13.22-1.el6cf.noarch
aeolus-all-0.13.22-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.13.22-1.el6cf.noarch