Bug 994871 - Got unknown error when define a bond with bond monitor mode as 'miimon' from virt-manager
Got unknown error when define a bond with bond monitor mode as 'miimon' from ...
Status: CLOSED DUPLICATE of bug 1067062
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: netcf (Show other bugs)
6.5
x86_64 Linux
medium Severity medium
: rc
: ---
Assigned To: Laine Stump
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-08 03:26 EDT by EricLee
Modified: 2014-04-14 07:00 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-04-14 07:00:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description EricLee 2013-08-08 03:26:35 EDT
Description of problem:
Got unknown error when define a bond with bond monitor mode as 'miimon' from virt-manager

Version-Release number of selected component (if applicable):
libvirt-0.10.2-21.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.384.el6.x86_64

How reproducible:
100%

Steps:
Virt-manager -> Connection Details-> Network Interface-> Add Interface-> select Bond as interface type-> 'onboot' as start mode -> Bond mode Configuration-> Bond mode='balance-tlb' and Bond monitor mode='miimon' -> select bond interface from host interface(like eth0 and eth1) -> Finish.

you will get:
error: An error occurred, but the cause is unknown

If not, virsh iface-dumpxml bond --inactive will get that error too.

# ifconfig will do not list the interface bond, as it is in wrong status.

Actual results:
as steps

Expected results:
work well

Additional info:
there is a related bug 879055 and 921621, but those bug are focus on when the bond0 interface is inactive and dumpxml with --inactive got error:
error: XML error: bond interface misses the bond element, so they are not the same issue.

BTW, I can not reproduce this issue on rhel7.0 with packages:
libvirt-1.1.1-1.el7.
Comment 4 Laine Stump 2014-04-14 07:00:20 EDT
Actually this was a bug in libvirt, and is being tracked in a separate BZ (already fixed upstream and in RHEL7)

*** This bug has been marked as a duplicate of bug 1067062 ***

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