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

Bug 859538

Summary: stop instances and they restart
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED DUPLICATE QA Contact: Rehana <aeolus-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: jprovazn, morazi
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: 2012-09-24 07:15:44 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:

Description Dave Johnson 2012-09-21 19:21:53 UTC 
Description of problem:
===========================
Rehana noticed that when she stopped a rhevm instance, the instance stopped, the blueprint status changed to stopped, and then the instance restarts.  I reproduced on a seperate system.   Checking vSphere/ec2 right now but rhevm definitely seems to exhibit this behavior.


Version-Release number of selected component (if applicable):
aeolus-all-0.13.8-1.el6cf.noarch
aeolus-conductor-0.13.8-1.el6cf.noarch
aeolus-conductor-daemons-0.13.8-1.el6cf.noarch
aeolus-conductor-doc-0.13.8-1.el6cf.noarch
aeolus-configure-2.8.6-1.el6cf.noarch
rubygem-aeolus-cli-0.7.1-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch


How reproducible:  100%


Steps to Reproduce:
1.   launch deployment consisting of pushed rhevm image
2.   allow to start
3.   stop it
4.   wait 5 minutes and notice it restarted
5.   check deployment state
6.   check rhevm console, it is running
Comment 2 Jan Provaznik 2012-09-24 07:15:44 UTC 
Despite different description, this is same bug as https://bugzilla.redhat.com/show_bug.cgi?id=857542 - a patch for this should be already pushed to master and 1.1 branches.

*** This bug has been marked as a duplicate of bug 857542 ***