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.
DescriptionJan Pokorný [poki]
2010-09-21 20:55:13 UTC
Description of problem:
There are two subproblems:
A. username can be optionally defined twice (per device instance and per node) while this ability to define the same parameter on both places is:
- unique across Luci (this should be presently the only such case which can be strange to the user)
- not necessary (it does not make much sense to define it twice, although
optionally)
(note: per-node username setting does not even work, but at least, user is offered with setting it on this place)
B. according to the code of fence_egenera, the key parameter to set username is "user", but Luci uses "username" (related problem is missing information about how to set username in fence_egenera man page, see bug #635824)
Version-Release number of selected component (if applicable):
luci-0.22.2-14.el6.x86_64
How reproducible:
Always.
Steps to Reproduce (how to input username information twice while the incorrect parameter "username" instead of "user" is used):
1. go to "Fence Devices", select Add, choose the Egenera device
2. *now you can set also username*, do it and when other fields are filled, submit the form
3. now go "Nodes" tab, click on certain node, in its details add a fencing method (if no one currently present), from within this method, click "Add a Fence Instance", here, select just added fence device instance
4. *now you can set also username*, do it (although this one will not be propagated to the cluster.conf as mentioned in description)
Actual results:
Username setting was shown on two different places and cluster.conf contains something like this:
(...)
<clusternode name="node1" nodeid="1" votes="1">
<fence>
<method name="test_method">
<device name="test_egenera"/>
</method>
</fence>
</clusternode>
(...)
<fencedevices>
<fencedevice agent="fence_egenera" cserver="localhost" name="test_egenera" username="username_global"/>
</fencedevices>
Expected results:
Username setting was shown only at on place (presumably in per device instance configuration) and in the parameter "user" was used instead of "username", i.e. cluster.conf from above should look like this:
(...)
<clusternode name="node1" nodeid="1" votes="1">
<fence>
<method name="test_method">
<device name="test_egenera"/>
</method>
</fence>
</clusternode>
(...)
<fencedevices>
<fencedevice agent="fence_egenera" cserver="localhost" name="test_egenera" user="username_global"/>
</fencedevices>
Additional info:
To verigy the fix, no Egenera hardware should be needed, checking Luci interactively and watching cluster.conf should be enough.
Comment 2Jan Pokorný [poki]
2010-09-23 18:46:45 UTC
(In reply to comment #0)
Not so important, but the cluster.conf snippets given in a bug description cannot be generated by Luci because of mandatory "lpan" and "pserver" parameters.
Hence, I should have used:
<device lpan="test_lpan" name="test_egenera" pserver="test_pserver"/>
instead of bare:
<device name="test_egenera"/>
Comment 3Jan Pokorný [poki]
2010-09-23 18:52:28 UTC
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-2011-0655.html
Description of problem: There are two subproblems: A. username can be optionally defined twice (per device instance and per node) while this ability to define the same parameter on both places is: - unique across Luci (this should be presently the only such case which can be strange to the user) - not necessary (it does not make much sense to define it twice, although optionally) (note: per-node username setting does not even work, but at least, user is offered with setting it on this place) B. according to the code of fence_egenera, the key parameter to set username is "user", but Luci uses "username" (related problem is missing information about how to set username in fence_egenera man page, see bug #635824) Version-Release number of selected component (if applicable): luci-0.22.2-14.el6.x86_64 How reproducible: Always. Steps to Reproduce (how to input username information twice while the incorrect parameter "username" instead of "user" is used): 1. go to "Fence Devices", select Add, choose the Egenera device 2. *now you can set also username*, do it and when other fields are filled, submit the form 3. now go "Nodes" tab, click on certain node, in its details add a fencing method (if no one currently present), from within this method, click "Add a Fence Instance", here, select just added fence device instance 4. *now you can set also username*, do it (although this one will not be propagated to the cluster.conf as mentioned in description) Actual results: Username setting was shown on two different places and cluster.conf contains something like this: (...) <clusternode name="node1" nodeid="1" votes="1"> <fence> <method name="test_method"> <device name="test_egenera"/> </method> </fence> </clusternode> (...) <fencedevices> <fencedevice agent="fence_egenera" cserver="localhost" name="test_egenera" username="username_global"/> </fencedevices> Expected results: Username setting was shown only at on place (presumably in per device instance configuration) and in the parameter "user" was used instead of "username", i.e. cluster.conf from above should look like this: (...) <clusternode name="node1" nodeid="1" votes="1"> <fence> <method name="test_method"> <device name="test_egenera"/> </method> </fence> </clusternode> (...) <fencedevices> <fencedevice agent="fence_egenera" cserver="localhost" name="test_egenera" user="username_global"/> </fencedevices> Additional info: To verigy the fix, no Egenera hardware should be needed, checking Luci interactively and watching cluster.conf should be enough.