Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1483448

Summary: Host stuck in Connecting state and spamming log if Vdsm reports a bridge with two NICs attached
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: bugs, danken, dholler
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-23 14:51:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log none

Description Michael Burman 2017-08-21 07:23:51 UTC 
Created attachment 1316122 [details]
engine log

Description of problem:
Engine can't handle a scenario of a Bridge with two ports.

In case of a bridge with 2 ports, engine can't handle it and host become in connecting state for ever. Endless loop.

2017-08-21 10:12:50,423+03 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (DefaultQuartzScheduler2) [4e95eb9f] Failure to refresh host 'silver-vdsb.qa.lab.tlv.redhat.com' runtime info: CallableS
tatementCallback; SQL [{call insertvds_interface(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}]; ERROR: duplicate key value violates unique constraint "vds_interface_vds_i
d_network_name_unique"
  Detail: Key (vds_id, network_name)=(e005432e-f713-4a4b-9718-76785f0ed83c, m4) already exists.
  Where: SQL statement "INSERT INTO vds_interface (


Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170820180837.git59243e9.el7.centos

How reproducible:
100% 

Steps to Reproduce:
1. Attach vlan tagged network to host via setup networks
2. On the host, manually edit the vlan interface with different tag(ifcfg file)
3. Restart network service

Actual results:
Host stuck in connecting loop. Engine can't handle such scenario.
Exceptions in engine.log

Expected results:
Engine should handle it. 

Additional info:
See also BZ 1470696
Comment 1 Michal Skrivanek 2020-03-19 15:42:23 UTC 
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it.
If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.
Comment 2 Dominik Holler 2020-03-23 14:51:46 UTC 
This is an edge case, which cannot be reached via oVirt.