Created attachment 604790 [details] translation_err Description of problem: Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.login to conductor 2.go to Administer --> Environments 3.Click on Provider selection Actual results: Observed that "translation missing: en.strategies.strict_order.name" is displayed for the Strategies name(PFA:translation_err.png) Expected results: Should display appropriate strategy name Additional info: rpm -qa | grep aeolus rubygem-aeolus-cli-0.7.0-0.20120815230025gitd64d64f.fc16.noarch aeolus-conductor-0.13.0-0.20120816030008gite8ea044.fc16.noarch aeolus-configure-2.8.0-0.20120815230023gitbdcd549.fc16.noarch aeolus-conductor-daemons-0.13.0-0.20120816030008gite8ea044.fc16.noarch rubygem-aeolus-image-0.6.0-0.20120815230028git25b7466.fc16.noarch aeolus-conductor-doc-0.13.0-0.20120816030008gite8ea044.fc16.noarch aeolus-all-0.13.0-0.20120816030008gite8ea044.fc16.noarch
Patch on list: https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-August/012140.html
in 1.1 branch: commit c0c7a7ec9ab42f2cbbf776c0d5859b470fa6d57b Author: Imre Farkas <ifarkas> Date: Thu Aug 16 16:21:06 2012 +0200 Fix RPM building for penalty for failure strategy Also fixes BZ#848633 https://bugzilla.redhat.com/show_bug.cgi?id=848633 (cherry picked from commit 87a617853ed5bfe500283d84559a76cbe4120dc9)
Created attachment 613938 [details] strategy_name Its Displaying the strategy name Updating the steps Steps to Reproduce: 1.login to conductor 2.go to Administer --> Clouds 3.Click on Edit button opposite any CRZ 4.Click on Cloud resource provider selection button PFA
Verified on rpm -qa | grep aeolus aeolus-conductor-doc-0.13.7-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-0.13.7-1.el6cf.noarch aeolus-all-0.13.7-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-daemons-0.13.7-1.el6cf.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-1516.html