Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: Navigate to default cloud->Role assignment->Grant access. Pool family text displayed.see attached screenshot. Expected results: Pool family to be replaced with Cloud Additional info: rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-10.el6.noarch aeolus-conductor-daemons-0.8.0-38.el6.noarch aeolus-all-0.8.0-38.el6.noarch rubygem-aeolus-cli-0.3.0-11.el6.noarch aeolus-conductor-doc-0.8.0-38.el6.noarch aeolus-configure-2.5.0-15.el6.noarch aeolus-conductor-0.8.0-38.el6.noarch
Created attachment 566447 [details] pool family
The reusable permissions panel references the model object type for display -- which would include Deployable, PoolFamily, etc. The fix is the same as for 798501 -- we need i18n strings for the classnames.
commit 90393e54cf96df58a2b4c2960abef14bcaa9c743 Author: Jason Guiditta <jguiditt> Date: Fri Mar 2 16:21:54 2012 -0500 BZs #798501 and #798505: Object names should be pulled from mapping file https://bugzilla.redhat.com/show_bug.cgi?id=798505 https://bugzilla.redhat.com/show_bug.cgi?id=798501 This boils down to the following: The strings in question were NOT being internationalized, they were pulled from the class names. This patch adds a mapping i18n file, which fixes both bugs (and any similar) and future ones saying we don't internationalize the class names. It is possible there are other cases beside permissions where this maybe be the case, but if so, it is a simple matter of repeating the pattern here and add a few translation strings to this file.
This has been pushed to master
Pool family text is still displayed.see attached screenshot. #rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-conductor-doc-0.8.3-1.el6.noarch aeolus-all-0.8.3-1.el6.noarch aeolus-conductor-daemons-0.8.3-1.el6.noarch aeolus-configure-2.5.2-1.el6.noarch aeolus-conductor-0.8.3-1.el6.noarch
Created attachment 572213 [details] ref pool family
After I fixed this last time, my fix was then overriden by a different approach. This works for me when testing against HEAD of product, so should make it back into the next build/puddle *** This bug has been marked as a duplicate of bug 803628 ***