Description of problem: When adding a rsa II fencing device via luci for a
cluster it has a field for entering the hostname vice the IP address.
Version-Release number of selected component (if applicable):
How reproducible: Every time it is used.
Steps to Reproduce:
1. Add a fence device
2. Choose the IBM RSA II
3. Field name is hostname and that is what is added to cluster.conf
Actual results: hostname is listed instead of ipaddr and when trying to fence a
node, the results are "failed" due to not being able to reference the ipaddr.
Expected results: The fence device uses ipaddr and not hostname.
Additional info: jparsons has produced a fix which hasn't been implemented at
the client site yet.
the field in the GUI is labeled "Hostname".
But the option in cluster.conf is correctly named "ipaddr".
Is a fqdn hostname truly useful, or does the fencing device require a
dotted-quad IP addres?
I thought this issue had been resolved a month ago?
The Luci GUI is labeled hostname, and can take either a hostname or an IP
address. The problem is in the cluster.conf. The Luci GUI will write out the
value of this field (either hostname or ip addr) as hostname=a.b.c.d (incorrect)
instead of ipaddr=a.b.c.d (correct). The daemon that runs on the clustered
machine will call the fencing agent with no parameters, ignoring the hostname=
fix looks good per comment 5
changing bug state to verified.
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 the 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.