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.

+++ 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 mgrac on 2012-03-26 08:40:06 EDT ---

Fixed in upstream:

http://git.fedorahosted.org/git/?p=fence-agents.git;a=commit;h=aefb817f08bfa8f2f1b1c1270ad4d697649fa40c

--- Additional comment from nstraz 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

fence_brocade
fence_drac
fence_egenera
fence_kdump
fence_scsi

Should these fence agents be fixed too?

Fix is now in upstream:

http://git.fedorahosted.org/git/?p=fence-agents.git;a=commit;h=87cbe09e06ce8a5fb578cffe21b3d2137d5f0e17

Unit test:

./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.

http://rhn.redhat.com/errata/RHBA-2013-0286.html

Note that unique="0" could be omitted algotgether: [1,2]

[1] https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/ra-api-1.dtd#L18
[2] https://github.com/ClusterLabs/resource-agents/blob/master/rgmanager/src/resources/ra-api-1-modified.dtd#L28