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.
DescriptionOliver Freyermuth
2020-11-26 16:22:54 UTC
Description of problem:
Trying:
pcs resource create vlan_83 ocf:heartbeat:iface-vlan vlan_interface=bond_in vlan_id=83 vlan_name=bond_in.83 vlan_loose_binding=true --group fw
pcs resource create vlan_84 ocf:heartbeat:iface-vlan vlan_interface=bond_in vlan_id=84 vlan_name=bond_in.84 vlan_loose_binding=true --group fw
yields:
Error: Value 'bond_in' of option 'vlan_interface' is not unique across 'ocf:heartbeat:iface-vlan' resources. Following resources are configured with the same value of the instance attribute: 'vlan_85', use --force to override
However, this is a common usecase, since vlan_name will naturally still be unique, i.e. the following VLAN interfaces could be created:
bond_in.83@bond_in
bond_in.84@bond_in
It also seems the vlan_id field is marked unique.
Version-Release number of selected component (if applicable):
4.1.1-44
How reproducible:
Always.
Steps to Reproduce:
1. pcs resource create vlan_83 ocf:heartbeat:iface-vlan vlan_interface=bond_in vlan_id=83 vlan_name=bond_in.83 vlan_loose_binding=true --group fw
2. pcs resource create vlan_84 ocf:heartbeat:iface-vlan vlan_interface=bond_in vlan_id=84 vlan_name=bond_in.84 vlan_loose_binding=true --group fw
Actual results:
Error.
Expected results:
Success.
Additional info:
The issue has already been reported upstream:
https://github.com/ClusterLabs/resource-agents/issues/1581
and a fix has been developed and merged:
https://github.com/ClusterLabs/resource-agents/pull/1586
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 (Moderate: resource-agents security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:4139
Description of problem: Trying: pcs resource create vlan_83 ocf:heartbeat:iface-vlan vlan_interface=bond_in vlan_id=83 vlan_name=bond_in.83 vlan_loose_binding=true --group fw pcs resource create vlan_84 ocf:heartbeat:iface-vlan vlan_interface=bond_in vlan_id=84 vlan_name=bond_in.84 vlan_loose_binding=true --group fw yields: Error: Value 'bond_in' of option 'vlan_interface' is not unique across 'ocf:heartbeat:iface-vlan' resources. Following resources are configured with the same value of the instance attribute: 'vlan_85', use --force to override However, this is a common usecase, since vlan_name will naturally still be unique, i.e. the following VLAN interfaces could be created: bond_in.83@bond_in bond_in.84@bond_in It also seems the vlan_id field is marked unique. Version-Release number of selected component (if applicable): 4.1.1-44 How reproducible: Always. Steps to Reproduce: 1. pcs resource create vlan_83 ocf:heartbeat:iface-vlan vlan_interface=bond_in vlan_id=83 vlan_name=bond_in.83 vlan_loose_binding=true --group fw 2. pcs resource create vlan_84 ocf:heartbeat:iface-vlan vlan_interface=bond_in vlan_id=84 vlan_name=bond_in.84 vlan_loose_binding=true --group fw Actual results: Error. Expected results: Success. Additional info: The issue has already been reported upstream: https://github.com/ClusterLabs/resource-agents/issues/1581 and a fix has been developed and merged: https://github.com/ClusterLabs/resource-agents/pull/1586