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

Bug 831496

Summary: Instance going to stopped state soon after launching on rhevm provider(south cluster), with out showing any error message on the UI
Product: [Retired] CloudForms Cloud Engine Reporter: Rehana <redakkan>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: dajohnso
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
dcloud_log
none
cluster none

Description Rehana 2012-06-13 06:57:50 UTC 
Created attachment 591368 [details]
dcloud_log

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Login to conductor
2.created a fronted cluster mapped to 'rhevm-default: South'(PFA: cluste.png)
3.Launch instance using this cluster
  
Actual results:
Observed that soon after launching, the instance went to stopped state, attaching the deltacloud log(PFA:dcloud.log)

Expected results:
Any such exception should be handled, and should display appropriate error message on conductor


Additional info:
rpm -qa | grep aeolus
aeolus-configure-2.5.7-1.el6_3.noarch
aeolus-all-0.8.27-1.el6_3.noarch
aeolus-conductor-0.8.27-1.el6_3.noarch
aeolus-conductor-doc-0.8.27-1.el6_3.noarch
aeolus-conductor-daemons-0.8.27-1.el6_3.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.3-1.el6_3.noarch
Comment 1 Rehana 2012-06-13 06:58:16 UTC 
Created attachment 591370 [details]
cluster