Bug 761119

Summary:	create new pool within family should pre-select correct family
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Dave Johnson <dajohnso>
Component:	aeolus-conductor	Assignee:	Imre Farkas <ifarkas>
Status:	CLOSED ERRATA	QA Contact:	wes hayutin <whayutin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0.0	CC:	akarol, athomas, deltacloud-maint, ifarkas, 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-05-15 21:18:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dave Johnson 2011-12-07 17:51:17 UTC

Description of problem:
==============================
On the Administer tab -> Environments you can create a new Pool Family and then you can add a new pool to the family.  When clicking on the 'New Pool' link, a generic create new pool page is displayed where the user still has to select which pool family to add the new pool too.  

Thinking we should pre-select the pool family based on the create 'New Pool' button of the Pool Family. 


Version-Release number of selected component (if applicable):
===============================================================
aeolus-all-0.7.0-4.el6.noarch
aeolus-conductor-0.7.0-4.el6.noarch
aeolus-conductor-daemons-0.7.0-4.el6.noarch
aeolus-conductor-doc-0.7.0-4.el6.noarch
aeolus-configure-2.4.0-3.el6.noarch
rubygem-aeolus-cli-0.2.0-3.el6.noarch
rubygem-aeolus-image-0.2.0-1.el6.noarch

Comment 1 Imre Farkas 2011-12-16 14:41:51 UTC

The issue has been fixed. Please verify the commit 53ccabea83c7a2ad2ad74b086db35f8315020f75

Comment 2 Aziza Karol 2011-12-28 10:31:47 UTC

Pool family is pre-selected based on the create 'New Pool'
button of the Pool Family. 

verified on:
[root@dell-pe2950-1 ~]# rpm -qa | grep aeolus
aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch
rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch
rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch
aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch
aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch

Comment 3 wes hayutin 2012-01-03 16:09:37 UTC

bugs in verified, removing from ce-sprint-next

Comment 5 errata-xmlrpc 2012-05-15 21:18:05 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