Bug 720023

Summary: creating a pool in the same pool family mirrors all the instances in the pool
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-conductorAssignee: Tomas Hrcka <thrcka>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 0.3.1CC: dajohnso, deltacloud-maint, slinaber, ssachdev, thrcka
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: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description wes hayutin 2011-07-08 18:23:44 UTC
Description of problem:
[root@sgi-xe310-02 ~]# rpm -qa | grep aeolus
aeolus-conductor-0.3.0-0.el6.20110708135911gitdb1097c.noarch
rubygem-aeolus-cli-0.0.1-1.el6.20110708135911gitdb1097c.noarch
aeolus-all-0.3.0-0.el6.20110708135911gitdb1097c.noarch
aeolus-configure-2.0.1-0.el6.20110707131907gitfaa220b.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110708135911gitdb1097c.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110708135911gitdb1097c.noarch


recreated this again.. I was hoping it was a fluke w/ my system.
recreate

1. setup conductor, and start a deployable in the default pool
2. create a new pool in the default pool family
3. expand the new pool or go to list view

Notice the original deployment is also listed in the new pool.

I spoke w/ Hugh about it, just to make sure that was not some design that I was unfamiliar w/. 

The bug is fixed when you create a new pool and it does not mirror deployments from other pools.

Comment 1 wes hayutin 2011-07-12 17:56:04 UTC
need a status on this please

Comment 2 Tomas Hrcka 2011-07-13 07:42:24 UTC
patch is in mailing list waiting for review and push

Comment 3 Tomas Hrcka 2011-07-13 11:39:10 UTC
please verify commit hash is 8e03373b77d9ec9f467714602455400e8b99291b

Comment 4 wes hayutin 2011-07-22 13:45:54 UTC
moving verified bugs off the tracker

Comment 5 wes hayutin 2011-08-01 19:59:07 UTC
release pending...

Comment 6 wes hayutin 2011-08-01 19:59:29 UTC
release pending.. 2

Comment 7 wes hayutin 2011-08-01 19:59:53 UTC
release pending...

Comment 9 wes hayutin 2011-12-08 13:57:07 UTC
perm close

Comment 10 wes hayutin 2011-12-08 13:59:43 UTC
closing out old bugs