Bug 797303

Summary: started instances after stopping everything
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED NOTABUG QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: low    
Version: 1.0.0CC: akarol, deltacloud-maint, ssachdev
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-02-24 21:02:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screenshot none

Description Dave Johnson 2012-02-24 21:01:22 UTC
Created attachment 565673 [details]
screenshot

Description of problem:
=============================
I launch a blueprint that contains 20 assemblies but only 13 of them started due to memory limitations.  That left 7 in a stopped state.

On the blueprint scorecard page, I then went to list view, checked all 20 instances, and stopped them.


Version-Release number of selected component (if applicable):
================================================================
aeolus-conductor-0.8.0-35.el6.noarch

Comment 1 Dave Johnson 2012-02-24 21:02:35 UTC
grr, got my tabs mixed up, I wasn't ready to log this yet... closing as not a bug