Description of problem: If non-required network is attached to bond and bonded NICs go down, host is marked as non-operational despite the fact network is non-required. Version-Release number of selected component (if applicable): 3.1.0-9.el6ev How reproducible: 100% Steps to Reproduce: 1.Clusters -> your cluster -> logical networks -> add network -> fill in name -> click OK 2.Clusters -> your cluster -> logical networks -> Assign/UnAssign Networks -> uncheck required on network from step 1 -> click OK 3.Hosts -> your host (with all interfaces up) -> network interfaces -> setup hosts networks -> create bond (mode 1)-> assign network from step 1 to bond 4.ssh to host and put bond interfaces down ((ifdown eth2 & ifdown eth3)or (physically disconnected the cable)) 5) host will be marked as non-operational despite network is non-required Actual results: host goes non-operational when non-required network is down Expected results: host does NOT go non-operational when non-required network is down Additional info: Event : Host zeus-vds2 moved to Non-Operational state because interfaces 'eth3, eth1' are down which needed by networks '<UNKNOWN>' in the current cluster happens only when the interfaces(eth2,eth3) are down happens only when network from step 1 is assigned to bond
Created attachment 601548 [details] engine log
Proposed fix in: http://gerrit.ovirt.org/#/c/6902/
Fixed in: 99c25d892c7896d2563d8365761d4952d7417f5e.
Verified in SI14