Description of problem: When an application blueprint which includes a service is launched and the provides/requires parameters do not match the aeolus-audrey-agent waits endlessly for the parameters and no messages are delivered to the user in the user interface informing them why the services did not execute. How reproducible: launch an application blueprint with several images and reference parameters that are not provided. Actual results: /usr/bin/audrey hangs and logs to /var/log/audrey.log a repetitive message which is not informative of what it is waiting for. Expected results: At a minimum, log what parameters are missing. Ideally, send this information to the user through the user interface.
We'd like to look at this for 1.1. Implementation notes: would add code to conductor to validate the deployable pre-launch by matching "return" values to dependency parameters.
I think this shoudl have already had devel-ack, so moving it back.
Fixed for this is pushed in commit 2d73ff1f7e8818dc39cb63571c6d3c2da4ad7457
Created attachment 613834 [details] working [root@ibm-ls21-04 yum.repos.d]# rpm -qa | grep "aeolus-conductor" aeolus-conductor-doc-0.13.7-1.el6cf.noarch aeolus-conductor-daemons-0.13.7-1.el6cf.noarch aeolus-conductor-0.13.7-1.el6cf.noarch Verified
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-1516.html