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 711625

Summary: Unable to create a cluster of KVM guests
Product: Red Hat Enterprise Linux 6 Reporter: Thomas Cameron <tcameron>
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, cww, djansa, joshua, rdassen, rsteiger
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: luci-0.23.0-15.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 09:45:30 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.log none

Description Thomas Cameron 2011-06-08 00:17:20 UTC
Created attachment 503593 [details]
luci.log

Description of problem:
KB article https://access.redhat.com/kb/docs/DOC-45145 describes defining a cluster service with a resource of a vm:

# Use a web browser to access the luci management application that administers this cluster
# Click "Clusters"
# Click the name of the cluster in question
# Click "Services"
# Click "Add"
# Enter the name of the virtual machine (as it appears in virsh list --all) into the "Service name" field
# Click "Add a resource"
# Select "Virtual Machine" from the drop down
# Enter /etc/libvirt/qemu into the "VM Configuration file path" field
# Click "Submit"

When I try, I get a 500 error and a traceback. I've attached luci.log

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

How reproducible:
# Click "Clusters"
# Click the name of the cluster in question
# Click "Services"
# Click "Add"
# Enter the name of the virtual machine (as it appears in virsh list --all) into the "Service name" field
# Click "Add a resource"
# Select "Virtual Machine" from the drop down
# Enter /etc/libvirt/qemu into the "VM Configuration file path" field
# Click "Submit"

Steps to Reproduce:
1.
2.
3.
  
Actual results:
500 error and traceback

Expected results:
Create a vm cluster

Additional info:

Comment 6 Ryan McCabe 2011-06-14 15:35:41 UTC
*** Bug 706553 has been marked as a duplicate of this bug. ***

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