Created attachment 575095 [details] deployable Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Login to conductor 2.Go to "monitor" 3.Select any CRZ 4.Go to 'Catalog images' section (PFA: deployable.png) Actual results: The reference to deployable was found Expected results: Should be changed to "application blueprints" Additional info: rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-0.8.7-1.el6.noarch aeolus-conductor-doc-0.8.7-1.el6.noarch aeolus-conductor-daemons-0.8.7-1.el6.noarch aeolus-configure-2.5.2-1.el6.noarch aeolus-all-0.8.7-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch
*** Bug 816039 has been marked as a duplicate of this bug. ***
Still the reference to "Deployable" is not changed to "Application blueprint" PFA:deployable.png 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
Created attachment 613922 [details] deployable on 1.1
Well this was a weird on. Those table headers weren't in en.yml at all. They were just random lowercase things combined with underscores that we displayed faithfully. Since this is after string freeze, I had to get a little creative with finding things to display. Will send a patch momentarily.
Patch on list: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-September/012624.html
ACK and pushed to master and 1.1: commit c39a698a55d8ea86d80cf0c036e6ba240c45d6f1 Author: Matt Wagner <matt.wagner> Date: Wed Sep 19 16:30:51 2012 -0400 BZ 809787 - Fixes untranslated table header For some reason this table header was never updated to use strings from en.yml, or even uppercase strings. Because it's after string freeze, I had to be slightly creative in fitting things in, so I left a comment suggesting that the keys I used might need cleanup later. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=809787 but is equally as useful upstream. Signed-off-by: Tzu-Mainn Chen <tzumainn> (cherry picked from commit 5b295d28e935da8b46da5a68547bb8af23f43a42)
1.Login to conductor 2.Go to "monitor" 3.Select any CRZ 4.Go to 'Catalog images' section (PFA: deployable.png) Problem is still there reference to 'deployable' found on above page,marking as assigned. [root@dhcp201-113 ~]# rpm -qa|grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.13.8-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch [root@dhcp201-113 ~]#
Created attachment 615412 [details] deployable
aeolus-conductor-0.13.8-1.el6cf.noarch was built on 2012-09-14, so the fix wouldn't be in. A recent conductor build should have the fix.
Created attachment 616881 [details] Appln_blueprint The above mentioned observation is fixed on rpm -qa | grep aeolus aeolus-conductor-doc-0.13.14-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.13.14-1.el6cf.noarch aeolus-conductor-0.13.14-1.el6cf.noarch rubygem-aeolus-cli-0.7.2-1.el6cf.noarch aeolus-configure-2.8.7-1.el6cf.noarch aeolus-conductor-daemons-0.13.14-1.el6cf.noarch moving to 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