Bug 798166
| Summary: | "Application blueprint admin" is not allowed to add a new application blue print | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Rehana <redakkan> | ||||
| Component: | aeolus-conductor | Assignee: | Scott Seago <sseago> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | pushpesh sharma <psharma> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 1.0.0 | CC: | akarol, athomas, bbandari, deltacloud-maint, ssachdev | ||||
| Target Milestone: | beta5 | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-08-30 17:17:14 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This user probably doesn't have catalog admin roles -- and you can't create an application blueprint without creating a catalog. Please revisit this after 788148 is pushed, because we have a new cloud-level Image Administrator that allows creation of app blueprints and images within the cloud. That probably serves the needed purpose here. We _may_ want to get rid of separate global catalog and app blueprint admin roles and have one global "Image and Application Admin" that allows build/push/blueprint across all clouds. If that's desired, I can do that under this bug. so as part of 788148 moving to onqa Note that, as described above, "Application Blueprint Admin" may still have this same problem. The suggestion under comment #1 was actually implemented in the fix for 800511. assigning to Pushpesh 1.local zone_application_blueprint_admin is able to do add application blue print from catalog-->Zone_specific_cat-->new application blueprint.It is not able to add new application blue print to any other catalog. 2.Global application_blueprint_admin is able to do add application blue print from catalog-->any_cat-->new application blueprint in all catalogs. Marking this bug as verified. |
Created attachment 566242 [details] Button Description of problem: I have made two observation in this bug 1. "Application blueprint administrator" is not allowed to add a new application blue print 2. The button name "New Deployable" from Edit application blueprint or edit Application blueprint.xml page should be changed to "New Application blueprint" (Button.png) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Created a new user "AppBPAdmin" with these privileges (zone global user,catalog global user,profile global user,and Application blueprint Administrator) 2.Log in to conductor as "AppBPAdmin" 3.Move to catalogs 4.click on "New Application Blueprint" button 5. On the conductor it displays an error msg "You have insufficient privileges to perform the selected action" Actual results: As a Application blueprint administrator, the user is allowed to do the following things 1. Edit application blueprint 2. Edit XMl 3. delete Application blueprint 4. Launch instances from Application blueprint But the user is not allowed to "Add Application blueprint" Expected results: Application blueprint administrator should be allowed to add "New application blueprint" Additional info: [root@intel-d3c69-01 ~]# rpm -qa | grep aeolus aeolus-conductor-0.8.0-36.el6.noarch aeolus-conductor-daemons-0.8.0-36.el6.noarch rubygem-aeolus-image-0.3.0-10.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-all-0.8.0-36.el6.noarch aeolus-conductor-doc-0.8.0-36.el6.noarch aeolus-configure-2.5.0-15.el6.noarch