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 705884

Summary: luci chokes on working cluster.conf line
Product: Red Hat Enterprise Linux 6 Reporter: joshua
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, jpokorny, rsteiger, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: luci-0.23.0-31.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 705876 (view as bug list) Environment:
Last Closed: 2011-12-06 09:45:14 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
luci error log
none
proposed patch none

Description joshua 2011-05-18 19:17:55 UTC
Created attachment 499675 [details]
luci error log

I have a cluster that works perfectly fine, then I add this line which also
works per the cluster, but on which luci chokes

vm autostart="1" exclusive="1" migrate="pause" name="Tally-On-Premise_2011.1"
path="/data/cluster-storage/tally" recovery="relocate"
snapshot="/data/cluster-storage/rally" use_virsh="1"/>

I get on another machine running RHEL6.1 beta, install luci, import the cluster, and luci in my web browser still shows the same error:

Error 500

We're sorry but we weren't able to process this request.



Per the /var/log/luci/luci.log, luci is very unhappy (see attached log).


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

luci-0.23.0-7.el6.x86_64


Expected Results:

Shouldn't luci be able to parse this line?  If not, surely it could have a more
intelligent response than the error above.

Comment 2 Lon Hohberger 2011-05-27 15:40:37 UTC
Do t

Comment 3 joshua 2011-05-27 17:17:56 UTC
?

Comment 4 Brian Brock 2011-06-07 21:20:50 UTC
Which option(s) is to blame for the misbehavior?

Can this be triggered with a cluster.conf only, with or without the system actually existing?

Comment 5 joshua 2011-06-07 21:54:35 UTC
It fails so immediately that it sure seems like luci is dying on the syntax

Comment 7 Ryan McCabe 2011-06-20 15:28:01 UTC
Created attachment 505645 [details]
proposed patch

Comment 20 errata-xmlrpc 2011-12-06 09:45:14 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