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.

Description of problem:
After create a bridge base on existing network device, the output message with a reverse order of the bridge and ethernet device name. 

Version-Release number of selected component (if applicable):
libvirt-0.9.10-2.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Use virsh command to create a bridge device
# virsh iface-bridge eth0 br0 --no-stp
Created bridge eth0 with attached device br0
Bridge interface br0 started


Actual results:
the output message with a reverse order of the bridge and ethernet device name. 

Expected results:
the output message should be:
Created bridge br0 with attached device eth0

Additional info:

Sorry, I forgot to post when I pushed the fix for this on Friday - there is a fix for this (literally one line) pushed upstream:

commit 4a92360091fd036152a7980f38ab01c54874061d
Author: Laine Stump <laine>
Date:   Fri Feb 24 14:32:33 2012 -0500

    virsh: fix informational message in iface-bridge command
    
    See: https://bugzilla.redhat.com/show_bug.cgi?id=797066
    
    The position of the bridge name and ethernet device name were
    accidentally swapped in the message informing of success creating the
    bridge.

I don't see any reason to delay this until 6.4, since it is a single line, is trivial to test, has 0 possibility of a merge conflict, and will eliminate confusion.

Bug verified.
# rpm -q libvirt
libvirt-0.9.10-3.el6.x86_64

# virsh iface-bridge eth0 br0 --no-stp
Created bridge br0 with attached device eth0
Bridge interface br0 started

# virsh iface-unbridge br0
Device eth0 un-attached from bridge br0
Interface eth0 started

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/RHSA-2012-0748.html