Bug 749579

Summary: default permissions for regular user cannot deploy image
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: chris alfonso <calfonso>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, calfonso, dajohnso, deltacloud-maint, dgao, hbrock, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dave Johnson 2011-10-27 15:29:48 UTC 
Description of problem:
====================================
Created a new user and left the default permissions alone.  By default new users are granted CatalogEntry Global User and Pool Global User.  I was under the impression (and maybe this is wrong) these default permissions would be sufficient for deploying images.  When I tried to deploy, was given and error stating hardware profile could not be found.

After granting HWP Administrator permission, the user could then deploy images.  Maybe we need a HWP GlobalUser role?


Version-Release number of selected component (if applicable):
============================================================================
aeolus-all-0.5.0-0.20111025005411git5ff5abd.fc15.noarch
aeolus-conductor-0.5.0-0.20111025005411git5ff5abd.fc15.noarch
aeolus-conductor-daemons-0.5.0-0.20111025005411git5ff5abd.fc15.noarch
aeolus-conductor-doc-0.5.0-0.20111025005411git5ff5abd.fc15.noarch
aeolus-configure-2.2.0-1.20111024205543gitf9232cc.fc15.noarch
Comment 1 chris alfonso 2011-11-03 00:59:16 UTC 
Not only was the hardware profile necessary, but also a catalog VIEW, USE permission is needed for the new deployment from a catalog menu.  I fixed both issues and posted it to the list for an ACK.
Comment 2 chris alfonso 2011-11-08 20:20:10 UTC 
6aca665dd8005aa695d89d35a2071ae2f2bb2448

conductor repo
Comment 3 wes hayutin 2011-11-10 19:47:21 UTC 
verified in 


[root@qeblade31 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.6.0-0.20111110145640gitd58f462.fc15.noarch
aeolus-conductor-0.6.0-0.20111110145640gitd58f462.fc15.noarch
aeolus-all-0.6.0-0.20111110145640gitd58f462.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111110100520gitbe66ffb.fc15.noarch
rubygem-aeolus-image-0.1.0-4.20111024205454git6b2b696.fc15.noarch
aeolus-configure-2.3.0-0.20111109080912git9fd4974.fc15.noarch
aeolus-conductor-daemons-0.6.0-0.20111110145640gitd58f462.fc15.noarch
aeolus-conductor-devel-0.6.0-0.20111110145640gitd58f462.fc15.noarch
Comment 4 wes hayutin 2011-11-28 01:16:48 UTC 
removing bugs from ce-sprint from the tracker.. you can find these bugs by querying the "qa whiteboard" for ce-sprint-60