Description of problem: When using luci to attempt to add an existing fence (hp ilo, was tried), an error is reported saying "A unique name must be provided for each Fence Device" Version-Release number of selected component (if applicable): [root@ra-vm3 ~]# cat /etc/redhat-release; uname -a; cman_tool version Red Hat Enterprise Linux Server release 5.2 (Tikanga) Linux ra-vm3.lab.bos.redhat.com 2.6.18-92.1.13.el5xen #1 SMP Thu Sep 4 04:07:08 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux 6.1.0 config 52 [root@ra-vm3 ~]# How reproducible: very Steps to Reproduce: 1. Remove existing fence 2. Update fence properties 3. Add fence, seleting existing fence Actual results: Error page is displayed, fence not added Expected results: Fence sucessfully added Additional info:
Steve, are you still seeing this issue and/or able to reproduce it? I can't seem to get it to reproduce with the RHEL 5.3.z build, and I wonder if it was fixed as a side effect of fixing another bug.
Created attachment 341622 [details] luci is unable to add gp-05-ipmi as a fence device for gp-05 using this config
i'm still hitting this bug. i've got a cluster which was previously managed with system-config-cluster, and luci is unable to work with the existing fence devices in this config. versions: [10:40:17 pjjw@gp-05:~]$ cat /etc/redhat-release ; uname -a ; sudo /usr/sbin/cman_tool version Red Hat Enterprise Linux Server release 5.3 (Tikanga) Linux gp-03.gs.washington.edu 2.6.18-128.1.1.el5xen #1 SMP Mon Jan 26 14:19:09 EST 2009 x86_64 x86_64 x86_64 GNU/Linux 6.1.0 config 144 steps to reproduce: 1. use above cluster.conf 2. select node gp-05.gs.washington.edu, and add the fence device gp-05-ipmi to the main fencing method. actual results: error page displayed, fence not added expected results: fence added. additional: i can work around this by deleting gp-05-ipmi from shared fence devices, then re-adding it in the node configuration window. i can't tell what's different, though, if anything, in cluster.conf when this is done.
caught in a lie! gp-05 is currently down for a rebuild, so I substituted gp-03's results, and it shows. however, i'm guessing the problem is with either luci or ricci, so i'll additionally submit that- server where luci runs is: [10:49:25][pjjw@manage-03:~]$ cat /etc/redhat-release ; uname -a ; rpm -q luciRed Hat Enterprise Linux Server release 5.3 (Tikanga) Linux manage-03.gs.washington.edu 2.6.18-92.1.18.el5 #1 SMP Wed Nov 5 09:00:19 EST 2008 x86_64 x86_64 x86_64 GNU/Linux luci-0.12.1-7.3.el5_3 ricci: [10:40:20 pjjw@gp-03:~]$ rpm -q ricci ricci-0.12.1-7.el5
fix verified, I can't reproduce the faulty behavior in luci-0.12.2-6.el5
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1381.html