Bug 743695 - Run state not listed for Deployment grid summary
Summary: Run state not listed for Deployment grid summary
Keywords:
Status: CLOSED ERRATA
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: chris alfonso
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-05 18:39 UTC by Joe Vlcek
Modified: 2016-02-01 02:35 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 22:14:42 UTC


Attachments (Terms of Use)
Run state in grid summary (247.17 KB, image/png)
2011-10-10 06:22 UTC, Aziza Karol
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description Joe Vlcek 2011-10-05 18:39:51 UTC
Description of problem:

Using Conductor UI when navigating to Pool/Deployments and selecting "Grid"
view the listed fields are: "Deployment Name", "Deployed on" (date), "Base Deployable", "Instances", "Pool", "Owner", "Provider"

State should also be there.

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


How reproducible:

see description
  
Actual results:

No state listed on Pools/Deployments "Grid" summary page. The user must select and open each "Deployment" in order to view it's current state, (running, failed, terminated...)


Expected results:

The Deployment State should be listed on the summary.
Even better would be to do something similar to EC2's "Show Hide" and allow the user to select what fields are displayed on the Deployment summary page.

Comment 2 chris alfonso 2011-10-06 13:53:56 UTC
commit 7931ee9cd1f0e3e98cb8370fcceee4140d4f8256
conductor.git repo

Comment 3 Aziza Karol 2011-10-10 06:21:47 UTC
Run state listed on Pools/Deployments "Grid" summary page.

See attached screenshot.

verified on:
[root@dell-pesc430-03 templates]# rpm -qa | egrep 'aeolus|imagefactory'
rubygem-imagefactory-console-0.5.0-4.20110824113238gitd9debef.fc15.noarch
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
aeolus-conductor-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-conductor-daemons-0.5.0-0.20111007200330gite77b251.fc15.noarch
imagefactory-jeosconf-ec2-fedora-0.1.0-1.fc15.noarch
aeolus-conductor-doc-0.5.0-0.20111007200330gite77b251.fc15.noarch
imagefactory-jeosconf-ec2-rhel-0.1.0-1.fc15.noarch
aeolus-all-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch
imagefactory-0.7.0-1.fc15.noarch

Comment 4 Aziza Karol 2011-10-10 06:22:40 UTC
Created attachment 527158 [details]
Run state in grid summary

Comment 6 errata-xmlrpc 2012-05-15 22:14:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html


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