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 598859 - Adding fence_xvm fence device through luci interface throws TypeError Traceback
Summary: Adding fence_xvm fence device through luci interface throws TypeError Traceback
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci
Version: 6.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 600039
TreeView+ depends on / blocked
 
Reported: 2010-06-02 08:27 UTC by Ryan Mitchell
Modified: 2010-11-10 22:10 UTC (History)
2 users (show)

Fixed In Version: luci-0.22.2-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 22:10:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Mitchell 2010-06-02 08:27:43 UTC
Description of problem:
When trying to create a fence_xvm device with name "myfence" on a new cluster with luci, luci interface displays "Error creating fence fence_xvm device".  

Traceback found in /var/log/luci/luci.log:
17:49:30,930 ERROR [luci.widget_validators.validate_fence] Error validating fence device fence_xvm
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/luci/widget_validators/validate_fence.py", line 633, in validate_fencedevice
    ret = FD_VALIDATE[fence_agent](fencedev, fence_name, **kw)
TypeError: val_noop_fd() takes exactly 1 non-keyword argument (2 given)


Version-Release number of selected component (if applicable):
luci-0.22.2-1.el6.x86_64
fence-virt-0.2.1-4.el6.x86_64

How reproducible:
Repeatable.

Steps to Reproduce:
1. Install Red Hat Enterprise Linux 6 Host (dom0), and 2x Red Hat Enterprise Linux 5 virtual guests (domU) in KVM.
2. Install luci on the RHEL6 host (dom0), and create an empty 2 node cluster on the 2 rhel5 guests.
3. Attempt to create fence_xvm device through luci interface (on RHEL6 dom0).

Actual results:
Error in Luci interface: "Error creating fence fence_xvm device"

Expected results:
Creates shared fence_xvm fence device.

Additional info:

Comment 2 RHEL Program Management 2010-06-07 16:01:19 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 6 releng-rhel@redhat.com 2010-11-10 22:10:55 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.