Red Hat Bugzilla – Bug 807342
confusing header error w/ insufficient permission to launch
Last modified: 2014-08-04 18:30:37 EDT
Created attachment 573087 [details]
Application launch failed!
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):
Added additional patch for master branch (previous is for 1.0-product branch):
This one is for 1.0-product:
BZ 807342 added src/config/locales/defaults
And this one is for master:
BZ 807342 added src/confic/locales/defaults
The product patch is what should be applied for release.
assigning to dgao
Created attachment 574625 [details]
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."
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.