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.

Bug 639120

Summary: Create "expert" user mode
Product: Red Hat Enterprise Linux 6 Reporter: Ryan McCabe <rmccabe>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: bbrock, cluster-maint, fdinitto, syeghiay, tao
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: luci-0.23.0-9.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 13:56:34 UTC 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 Ryan McCabe 2010-09-30 21:07:35 UTC
Create an expert user mode that will allow for configuration of everything in the schema. There's a lot of configuration we don't necessary want to expose to all users. When a user is in expert mode, everything will be exposed.

Comment 1 Perry Myers 2010-11-23 18:15:58 UTC
Can we list out on this bz:
* How we're going to enable/disable expert mode?
* What specific configuration elements/items will be exposed when expert mode is enabled?

Comment 2 Brian Brock 2010-12-01 22:00:21 UTC
Still need at least the information requested in comment 1 to test anything, staying in needinfo.

Also would be helpful to know any details about the widget that describe it.  Location in the menu system, whether it's on another page, and if there are any restrictions at all on the flag being turned on/off, like whether it must be associated with a cluster in the luci interface or if should be grayed out under any conditions.

Comment 8 Ryan McCabe 2011-03-17 15:55:45 UTC
*** Bug 688049 has been marked as a duplicate of this bug. ***

Comment 10 Fabio Massimo Di Nitto 2011-03-17 22:44:28 UTC
(In reply to comment #8)
> *** Bug 688049 has been marked as a duplicate of this bug. ***

Be careful that the TTL options is not available in 6.0. It's a new feature in 6.1 and it's not landed in corosync yet. It is allowed to configure it, but it will have no effect till corosync gets the patches (for QE).

Comment 14 Ryan McCabe 2011-04-01 17:35:25 UTC
*** Bug 601702 has been marked as a duplicate of this bug. ***

Comment 15 errata-xmlrpc 2011-05-19 13:56:34 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0655.html