Hide Forgot
Created attachment 573551 [details] ss1 Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Login to conductor 2.Go to catalogs--> Select any catalog 3.Select the Application blueprint 4. Check in 'Role assignment" section Actual results: Observed that role "Deployable user" was displayed instead of " Application Blueprint user" (PFA: ss1.png) Expected results: It should be changed to " Application Blueprint user" Additional info: rpm -qa | grep aeolus aeolus-conductor-0.8.3-1.el6.noarch aeolus-conductor-daemons-0.8.3-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configure-2.5.2-1.el6.noarch aeolus-all-0.8.3-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-conductor-doc-0.8.3-1.el6.noarch
nice find
This is to be addressed in a release note: https://bugzilla.redhat.com/show_bug.cgi?id=808535 The offending role isn't required, and will be removed.
Just checked and this is still present on 1.0.1
This issue is resolved, (PFA:Appln_blueprint_user.png) 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
Created attachment 613934 [details] Appln_blueprint_user