+++ This bug was initially created as a clone of Bug #806883 +++
Cloned to fix agents missed in 6.3.
Attribute unique in XML metadata (-o metadata) is set to TRUE (1) by default in all of the cases. "Unique" should be used only in situation where same value cannot be used across several agents. Fence agents do not have such kind of attributes so default value should be FALSE (0).
--- Additional comment from firstname.lastname@example.org on 2012-03-26 08:40:06 EDT ---
Fixed in upstream:
--- Additional comment from email@example.com on 2012-05-17 10:10:08 EDT ---
I looked through the metadata generated by all fence agents and found the following agents still produce unique parameters
Should these fence agents be fixed too?
Fix is now in upstream:
./fence_? -o metadata | grep unique
<parameter name="action" unique="0" required="1">
<parameter name="ipaddr" unique="0" required="1">
there should be no answer for
./fence_? -o metadata | grep 'unique="1"'
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.
Note that unique="0" could be omitted algotgether: [1,2]