Created attachment 557906 [details] ss Description of problem: 1. start an application, in fact start a couple 2. nav to the first application 3. export events get events for all applications Status_code;Event_time;Summary;Source_type;Description;Source_id ;2012-01-27 16:41:05 UTC;created;Instance;;5 ;2012-01-27 16:15:46 UTC;created;Instance;;2 pending;2012-01-27 16:15:51 UTC;state changed to pending;Instance;;2 running;2012-01-27 16:16:59 UTC;state changed to running;Instance;;2 ;2012-01-27 16:21:55 UTC;created;Instance;;4 pending;2012-01-27 16:21:59 UTC;state changed to pending;Instance;;4 stopped;2012-01-27 16:22:11 UTC;state changed to stopped;Instance;;4 pending;2012-01-27 16:22:13 UTC;state changed to pending;Instance;;4 running;2012-01-27 16:23:14 UTC;state changed to running;Instance;;4 ;2012-01-27 16:18:21 UTC;created;Instance;;3 pending;2012-01-27 16:18:28 UTC;state changed to pending;Instance;;3 running;2012-01-27 16:20:08 UTC;state changed to running;Instance;;3 ;2012-01-27 16:15:05 UTC;created;Instance;;1 expected results: exported events are for the "applicaition/s" in context. If I am only viewing one application export the one.. If I am viewing a list of applications.. export events for those applications. [root@qeblade30 ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.8.0-13.el6.noarch aeolus-configure-2.5.0-9.el6.noarch rubygem-aeolus-image-0.3.0-5.el6.noarch aeolus-all-0.8.0-13.el6.noarch aeolus-conductor-0.8.0-13.el6.noarch aeolus-conductor-daemons-0.8.0-13.el6.noarch rubygem-aeolus-cli-0.3.0-6.el6.noarch
Whilst multi-instance deployables aren't supported in 1.0, they shouldn't provide a means to circumvent quota limits. This should be fixed, by refusing to launch a deployable at all if it contains more instances than the quota limit currently permits. Launching a subset of the instances specified in the deployable definition is not a desirable solution.
Patch sent to the list: https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008697.html
Pushed to staging: commit 18f00af846f7d6a1608e51d7dcfa07bd662a302c Author: Tomas Sedovic <tomas> Date: Tue Feb 7 15:42:02 2012 +0100 BZ#785223 Limit export instances scope https://bugzilla.redhat.com/show_bug.cgi?id=785223 When exporting instances from the Deployments Details page, only the instances belonging to that deployment should be included in the CSV. Signed-off-by: Matt Wagner <matt.wagner>
Description;Status_code;Source_type;Summary;Event_time;Source_id ;;Instance;created;2012-02-08 05:36:53 UTC;1 ;pending;Instance;state changed to pending;2012-02-08 05:36:56 UTC;1 ;running;Instance;state changed to running;2012-02-08 05:38:21 UTC;1 ============================================ Only that instance is exported verified in 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
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