Bug 718355

Summary: Logging feature in Luci not working as expected
Product: Red Hat Enterprise Linux 6 Reporter: Kendrick Gay <kgay>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: bbrock, cluster-maint, edamato, kanderso, rmccabe, rsteiger, wburrows
Target Milestone: beta   
Target Release: 6.2   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: luci-0.23.0-30.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 09:45:38 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:
Attachments:
Description Flags
proposed patch none

Description Kendrick Gay 2011-07-01 21:58:32 UTC 
Description of problem:

Clustername -> Configure -> Logging

Any submission to textfield returns 500 error.  In addition, when you select "info" for message priority, both "Log fenced messages to syslog" and "Log fenced messages to log file" get unselected after clicking apply.

Moreover, if I set message priority to anything other than "info", both aforementioned checkboxes are automagically selected again after clicking apply.

Version-Release number of selected component (if applicable):
luci-0.23.0-13

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Logging under cluster Configure page
2. Elect daemon logging to manage and submit text to field
3. Click Apply
  
Actual results:

"Error 500 - We're sorry but we weren't able to process  this request."

Expected results:

Changes to logging are submitted.

Additional info:
Comment 1 Ryan McCabe 2011-07-02 03:45:30 UTC 
Created attachment 510962 [details]
proposed patch
Comment 11 errata-xmlrpc 2011-12-06 09:45:38 UTC 
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/RHBA-2011-1510.html