Created attachment 706446 [details] engine and vdsm logs Description of problem: I'm unable to add a vlan tagged bonded interface to the current configuration of a hyper-visor (node). Version-Release number of selected component (if applicable): Hyper-Visor: vdsm.x86_64 4.10.0-0.46.15.el6 @vdsm31-dre vdsm-cli.noarch 4.10.0-0.46.15.el6 @vdsm31-dre vdsm-python.x86_64 4.10.0-0.46.15.el6 @vdsm31-dre vdsm-xmlrpc.noarch 4.10.0-0.46.15.el6 @vdsm31-dre Engine: jpackage-utils.noarch 5.0.0-7.jpp6 @ovirt31-dre ovirt-engine.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-backend.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-cli.noarch 3.1.0.7-1.el6 @ovirt31-dre ovirt-engine-config.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-dbscripts.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-genericapi.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-jbossas711.x86_64 1-0 @ovirt31-dre ovirt-engine-notification-service.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-restapi.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-sdk.noarch 3.1.0.5-1.el6 @ovirt31-dre ovirt-engine-setup.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-tools-common.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-userportal.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-engine-webadmin-portal.noarch 3.1.0-3.19.el6 @ovirt31-dre ovirt-image-uploader.noarch 3.1.0-16.el6 @ovirt31-dre ovirt-iso-uploader.noarch 3.1.0-16.el6 @ovirt31-dre ovirt-log-collector.noarch 3.1.0-16.el6 @ovirt31-dre vdsm-bootstrap.noarch 4.10.0-0.46.15.el6 @vdsm31-dre How reproducible: Always Steps to Reproduce: Initial Setup - a) install centos 6.3 minimal b) add dreyou repo to host c) disable (change to permissive) selinux d) disable firewall e) share local storage of host (via nfs or iscsi) for use as storage domain f) setup network f.1) setup bonding config in /etc/modprobe.d/bonding.conf alias bond0 bonding options bond0 miimon=80 mode=4 f.2) setup interfaces cd /etc/sysconfig/network-scripts ifcfg-bond0: DEVICE=bond0 ONBOOT=yes BOOTPROTO=none BONDING_OPTS='mode=802.3ad miimon=150' NM_CONTROLLED=no ifcfg-bond0.111: VLAN=yes DEVICE=bond0.111 ONBOOT=yes BOOTPROTO=none USERCTL=no BRIDGE=ovirtmgmt ifcfg-bond0.112: VLAN=yes DEVICE=bond0.112 ONBOOT=yes BOOTPROTO=none USERCTL=no BRIDGE=br1 ifcfg-ovirtmgmt: DEVICE=ovirtmgmt TYPE=Bridge ONBOOT=yes DELAY=0 NM_CONTROLLED=no PEERROUTES=yes DEFROUTE=yes PEERDNS=yes BOOTPROTO=dhcp ONBOOT=yes ifcfg-br1: DEVICE=br1 TYPE=Bridge ONBOOT=yes DELAY=0 NM_CONTROLLED=no PEERROUTES=yes DEFROUTE=yes PEERDNS=yes BOOTPROTO=dhcp ONBOOT=yes ifcfg-eth0: DEVICE=eth0 ONBOOT=yes BOOTPROTO=none MASTER=bond0 SLAVE=yes NM_CONTROLLED=no ifcfg-eth1: DEVICE=eth1 ONBOOT=yes BOOTPROTO=none MASTER=bond0 SLAVE=yes NM_CONTROLLED=no g) rebooted the host to ensure all modules / interfaces /etc. are coming up correct h) install ovirt-engine 3.1 (from dreyou repo) onto another host / vm i) setup dc, cluster and add the host j) setup the storage domain, as you usually would (NFS or ISCSI, not relevant for this test) k) create a VM running on the host l) in webgui go to hosts -> Select your host -> Network Interfaces m) you should see a bond0 with bond0.111 and bond0.112 as vlans assigned (see screenshot: ovirt-engine-hosts-network-interfaces-initial-config.png) n) try adding another vlan tagged interface by going via : n.1) Clusters -> Select your cluster -> Logical Networks n.2) Select Add Network n.3) Enter name "br2", Tick "Enable VLAN tagging", Set tag to 113, Tick "VM Network", click OK o) You'll see the message "Network br2 attached to Cluster "ClusterName" p) Go back to Hosts -> Select your host -> Network Interfaces q) Select "Setup Host Networks" q.1) you can see the new network in unassigned logical networks q.2) drag it to be assigned to bond0 q.3) scroll down and tick "Save network configuration" q.4) click OK q.5) you'll get a message: "Error while executing action Setup Networks: Internal oVirt Engine Error" q.6) click "Close" q.7) click "Cancel" r) To keep a clean config, remove the logical network previously created from the cluster & dc Expected results: Interface added to HV/Node. Additional info:
Created attachment 706447 [details] ovirt-engine-hosts-network-interfaces-initial-config.png
I've gone through this yesterday together with Antoni Segura Puimedon and he suggested that the bug is visible in the 1st line of the VDSM.log - however - that it is the Engine causing the error.
This bug has been fixed by the fix for BZ909678.
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)