Bug 788550 - Not able to launch for realms from Monitor page
Summary: Not able to launch for realms from Monitor page
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-08 12:26 UTC by Shveta
Modified: 2012-08-30 17:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-30 17:12:48 UTC


Attachments (Terms of Use)
realm_launch (231.34 KB, image/png)
2012-02-08 12:26 UTC, Shveta
no flags Details

Description Shveta 2012-02-08 12:26:17 UTC
Created attachment 560249 [details]
realm_launch

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. created a realm for Rhev and one for Vsphere
2. Built and pushed for all providers
3. Monitor page , New application , selected rhev_realm 
and launch 
get the following error 
    Some component blueprints will not be launched:
    ssachdev: Cloud Resource Cluster vmware_realm is not mapped to any cloud resource provider or provider realm
    rhevmaccount: component outline is not pushed to this provider account
    vsphereaccount: component outline is not pushed to this provider account
    mock: component outline is not pushed to this provider account


Same thing if i try to do from Content- deployable it gets launched.
  
Actual results:


Expected results:


Additional info:
 rpm -qa|grep aeolus
aeolus-conductor-doc-0.8.0-23.el6.noarch
aeolus-configure-2.5.0-12.el6.noarch
aeolus-conductor-daemons-0.8.0-23.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-conductor-0.8.0-23.el6.noarch
aeolus-all-0.8.0-23.el6.noarch

Comment 1 wes hayutin 2012-02-22 23:46:10 UTC
moving version to 1.0.0 .  version = found in version

Comment 2 wes hayutin 2012-02-23 00:18:05 UTC
Shveta can you recreate?

Comment 4 Shveta 2012-02-23 05:36:06 UTC
Not getting the bug now ..

rpm -qa|grep aeolus
aeolus-conductor-daemons-0.8.0-33.el6.noarch
aeolus-configure-2.5.0-14.el6.noarch
rubygem-aeolus-image-0.3.0-8.el6.noarch
aeolus-conductor-0.8.0-33.el6.noarch
rubygem-aeolus-cli-0.3.0-9.el6.noarch
aeolus-conductor-doc-0.8.0-33.el6.noarch
aeolus-all-0.8.0-33.el6.noarch


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