Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
If a unprivileged user try to import a new cluster, he get a Error 403. However the cluster is created never the less.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 6.2 Beta (Santiago)
luci-0.23.0-29.el6.x86_64
How reproducible:
Steps to Reproduce:
1. Install cluster suit and luci
2. Create a cluster in luci
3. Delete the cluster in luci
4. Create a new local system user
5. Login to luci as this new user.
6. Import the cluster created before.
Actual results:
You get a "Error 403" but the cluster is importer.
Expected results:
You get a "Error 403" instead of the import wizard and the cluster is not imported.
Additional info:
I can't reproduce this. When I try to do this, I get the error 403, and the cluster is not added.
Comment 3RHEL Program Management
2011-10-18 18:40:13 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
I can't reproduce this either; I logged in as a non-root user, clicked 'homebase', then 'manage clusters', clicked 'add cluster', filled the form out, clicked submit and then was presented with:
====
[X] At least one of the following predicates must be met: The current user must be "root", The member must belong to at least one of the following groups: managers, import_cluster
Error 403
We're sorry but we weren't able to process this request.
====