Hide Forgot
Created attachment 560472 [details] logs Description of problem: This bug depends on 788700. When the Host was added to the cluster without MN, there is no way to attach MN to a "free" interface. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Same as Bug 788700 (same host) 2.Try to add MN (rhevm) to a "free" Host's NIC. (This time a rhevm MN is added on eth0 with IP 10.35.102.23) 3. Actual results: Failure to add the rhevm network to eth0. GUI: Unexpected exception (Error code:16) Expected results: Success in adding the rhevm MN. Additional info: BE and VDSM logs attached.
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Avi, please reproduce with current code base, and hopefully attach a more succinct vdsm.log with the error.
If the description is accurate, it's quite severe (and I recall customers asking about similar scenario), so asking for 6.3.z as well (once we understand the issue, that is).
I believe this problem is related to https://bugzilla.redhat.com/show_bug.cgi?id=812793 first problem is that rhevm tries to put vdsm 4.9.6-9 into host during install so adding rhevm interface fails (in all cases bond or no bond). After host install fails to add rhevm interface (rest of instllation process is ok), I have to replace vdsm 4.9.6-9 with vdsm 4.9.6-10 (both on rhevm side and host side). Than I can add rhevm management interface with use of SINGLE interface (no bond). If I tried the bond scenario. Adding rhevm interface during install failed (that was quite expected because of vdsm 4.9.6-9) 2012-05-21 12:50:43,481 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-10-thread-2) [15502c5e] Installation of 10.34.67.36. Recieved message: <BSTRAP component='SetNetworking' status='FAIL' message='addNetwork error trying to add management bridge'/> when I upgraded vdsm bootstrap to 4.9.6-10 on rhevm side and host to libvirt-0.9.10-18.el6.x86_64 libvirt-client-0.9.10-18.el6.x86_64 libvirt-debuginfo-0.9.10-18.el6.x86_64 libvirt-devel-0.9.10-18.el6.x86_64 libvirt-python-0.9.10-18.el6.x86_64 qemu-img-rhev-0.12.1.2-2.293.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.293.el6.x86_64 qemu-kvm-rhev-debuginfo-0.12.1.2-2.293.el6.x86_64 qemu-kvm-rhev-tools-0.12.1.2-2.293.el6.x86_64 vdsm-4.9.6-10.el6.x86_64 vdsm-cli-4.9.6-10.el6.noarch vdsm-python-4.9.6-10.el6.noarch I could not add rhevm interface to bond1, error message was that logical network does not exist. See screenshost in attachment, 2012-05-21 12:58:02,077 WARN [org.ovirt.engine.core.bll.UpdateNetworkToVdsInterfaceCommand] (ajp--0.0.0.0-8009-4) [715036f6] CanDoAction of action UpdateNetworkToVdsInterface failed. Reasons:NETWROK_NOT_EXISTS however I could add rhevm interface to single interface now, without complaint on non-existent logical network. 2012-05-21 13:20:11,994 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.AddNetworkVDSCommand] (ajp--0.0.0.0-8009-10) [76bc3307] START, AddNetworkVDSCommand(vdsId = 41ee3a80-a334-11e1-8688-001a4a013f0e, networkName=rhevm, oldNetworkName=null, hostAddr=null, checkConnectivity=false, connectionTimeout=0, vlanId=null, bondName=null, nics=[em1], inetAddr=10.34.66.61, networkMask=255.255.255.0, gateway=, stp=false, bondingOptions=null, bootProtocol=StaticIp), log id: 4b3d7c03 2012-05-21 13:20:16,454 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.AddNetworkVDSCommand] (ajp--0.0.0.0-8009-10) [76bc3307] FINISH, AddNetworkVDSCommand, log id: 4b3d7c03 bond1 config was following: [root@dell-r210ii-06 ~]# cat /etc/sysconfig/network-scripts/ifcfg-p1p1 DEVICE=p1p1 ONBOOT=yes BOOTPROTO=none MASTER=bond1 SLAVE=yes NM_CONTROLLED=no [root@dell-r210ii-06 ~]# cat /etc/sysconfig/network-scripts/ifcfg-p1p2 DEVICE=p1p2 ONBOOT=yes BOOTPROTO=none MASTER=bond1 SLAVE=yes NM_CONTROLLED=no [root@dell-r210ii-06 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond1 DEVICE=bond1 ONBOOT=yes BOOTPROTO=dhcp BONDING_OPTS=mode=2 NM_CONTROLLED=no logs are attached
Created attachment 585944 [details] vdsm.log + engine.log
Created attachment 585945 [details] screenshot
It seems that host installation via bond interface is not supported by vdsm-bootstrap-4.9.6-10.el6.noarch I tried to add host into setup via bonded interface and following message appeared in vds_bootstrap log. Tue, 22 May 2012 13:38:33 ERROR _getRHELBridgeParams Found bonding: bond1. This network configuration is notsupported! Please configure rhevm bridge manually and re-install. vds_bootstrap + engine.log + vdsm.log + ifcfg-bond0 attached
Created attachment 586038 [details] logs for comment 9
*** This bug has been marked as a duplicate of bug 531390 ***