Created attachment 573087 [details] deploy_fail Application launch failed! Header Pool must be enabled when trying to launch an instance that I don't have access to.
see screenshot in https://bugzilla.redhat.com/show_bug.cgi?id=807664
Patch created (adding in missing src/config/locales/defaults directory to the .spec file): http://post-office.corp.redhat.com/mailman/private/deltacloud-internal/2012-March/msg00135.html
Added additional patch for master branch (previous is for 1.0-product branch): https://fedorahosted.org/pipermail/aeolus-devel/2012-March/009726.html
Patches submitted. This one is for 1.0-product: commit f8bf08b434d1f910a0698701931524bf5abb775e BZ 807342 added src/config/locales/defaults And this one is for master: commit d9dda34bcc94fd99cc6289c0ac5dd4006901a92c BZ 807342 added src/confic/locales/defaults The product patch is what should be applied for release.
assigning to dgao
Created attachment 574625 [details] deploy_fail_2 Header is still confusing after patch.
Would it be possible to open a new ticket for this? The fundamental issue here seems to be different, and I'm guessing the steps to reproduce are different as well, as the previous error was a permissions error and this appears to be a hardware profile issue. Or if it's policy to continue with the same ticket, would it be possible to at least specify the steps to reproduce?
Actually this is still a permission issue. I simply created a user with no permission to access the hardware profile or anything for that matter. Upon launching the instance, I've bumped into the issue captured by the screenshot. Expected result: "Your account does not have sufficient permission to access the hardware profile needed to launch this instance."
Patch created: https://fedorahosted.org/pipermail/aeolus-devel/2012-April/009830.html
A user with cloud_image_admin role tries to launch the instance, standard error message is displayed "You have insufficient privileges to perform the selected action." I feel above observation is sufficient to mark the bug as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html