Bug 836992 - [RFE]- Display appropriate message when a multi-provider image application blueprint is created
[RFE]- Display appropriate message when a multi-provider image application bl...
Status: NEW
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-conductor (Show other bugs)
1.0.0
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Angus Thomas
Rehana
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-02 08:59 EDT by Rehana
Modified: 2012-09-28 13:11 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
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: ---


Attachments (Terms of Use)
SS1 (222.52 KB, image/png)
2012-07-02 08:59 EDT, Rehana
no flags Details

  None (edit)
Description Rehana 2012-07-02 08:59:07 EDT
Created attachment 595723 [details]
SS1

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Login to conductor
2.build and pushed an image to rhevm
3.build and pushed an image to vsphere
4.Created a multi instace application blueprint with above two images
  
Actual results:
The application blueprint got created, but the build status was "Images are not Built" for both the providers(PFA: SS1.png)

Expected results:
Should display appropriate error message

Additional info:

************chat with Jan *************

<rehana> and is it possible to launch multiinstance on diff providers using a single appln blueprint
<jprovazn> no ;)
<jprovazn> if one image is on rhevm
<jprovazn> and secon on vsphere
<jprovazn> it's not complete
<rehana> yea..
<jprovazn> to launch it somewhere
<jprovazn> you must have all images built&pushed on that provider

on

rpm -qa | grep aeolus
aeolus-configure-2.5.10-1.el6cf.noarch
aeolus-all-0.8.34-1.el6cf.noarch
aeolus-conductor-doc-0.8.34-1.el6cf.noarch
aeolus-conductor-daemons-0.8.34-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.3-2.el6_2.noarch
aeolus-conductor-0.8.34-1.el6cf.noarch

Note You need to log in before you can comment on or make changes to this bug.