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.
Bug 638619 - [RHEL6-Beta] 'virsh attach-interface' succeeds even if a duplicate MAC address is specified.
Summary: [RHEL6-Beta] 'virsh attach-interface' succeeds even if a duplicate MAC addres...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Laine Stump
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: GSS_6_2_PROPOSED
TreeView+ depends on / blocked
 
Reported: 2010-09-29 14:10 UTC by Sadique Puthen
Modified: 2018-11-14 19:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-17 18:02:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sadique Puthen 2010-09-29 14:10:00 UTC 
Description of problem:

Description of Problem:

"virsh attach-interface" succeeds as follows even if a duplicate MAC address is specified.

# virsh attach-interface vm1 bridge br0 --mac 02:17:42:2F:99:01
Interface attached successfully

# virsh attach-interface vm1 bridge br0 --mac 02:17:42:2F:99:01
Interface attached successfully

It should report an error message like "MAC address already attached"

Version-Release number of selected component:

Red Hat Enterprise Linux Version Number: 6
Release Number: snapshot13
Architecture: x86_64
Kernel Version: kernel-2.6.32-70.el6.x86_64
Related Package Version: libvirt-client-0.8.1-27.el6.x86_64


How reproducible:
Always

Steps to Reproduce:

# virsh attach-interface rhel6 bridge br0 --mac 02:17:42:2F:99:01
Interface attached successfully

# virsh attach-interface rhel6 bridge br0 --mac 02:17:42:2F:99:01
Interface attached successfully

Both command created vnet1 and vnet2 on the Host and a eth1 and eth2 on the guest with a mac address of 00:00:00:00:00:00 (which could be another bug). virsh dumpxml shows the duplicate macs are accepted.

    <interface type='bridge'>
      <mac address='02:17:42:2f:99:01'/>
      <source bridge='br0'/>
      <target dev='vnet1'/>
      <alias name='net1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </interface>
    <interface type='bridge'>
      <mac address='02:17:42:2f:99:01'/>
      <source bridge='br0'/>
      <target dev='vnet2'/>
      <alias name='net2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </interface>  

Actual results:

libvirt allows to specify duplicate macs

Expected results:

libvirt should allow to specify duplicate macs

Additional info:
Note You need to log in before you can comment on or make changes to this bug.