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.

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.

Do t

?

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?

It fails so immediately that it sure seems like luci is dying on the syntax

Created attachment 505645 [details]
proposed patch

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