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
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.
6aca665dd8005aa695d89d35a2071ae2f2bb2448 conductor repo
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
removing bugs from ce-sprint from the tracker.. you can find these bugs by querying the "qa whiteboard" for ce-sprint-60