Bug 1156234

Summary:	Network Driver error : Network not found: no network with matching name 'vdsm-NETNAME'
Product:	[Retired] oVirt	Reporter:	Yamakasi <yamakasi.014>
Component:	vdsm	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED NOTABUG	QA Contact:	Gil Klein <gklein>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	bazulay, bugs, ecohen, gklein, iheim, lsurette, mgoldboi, rbalakri, yamakasi.014, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-26 23:12:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yamakasi 2014-10-23 23:19:59 UTC

Description of problem:

VDSM Host is unreachable after installation and networks are failing.


Oct 23 23:13:22 servername kernel: bnx2 0000:02:00.0 enp2s0: using MSI
Oct 23 23:13:22 servername kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
Oct 23 23:13:22 servername kernel: device enp2s0 entered promiscuous mode
Oct 23 23:13:22 servername kernel: bnx2 0000:02:00.0 enp2s0: NIC SerDes Link is Up, 1000 Mbps full duplex
Oct 23 23:13:22 servername kernel:
Oct 23 23:13:22 servername kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
Oct 23 23:13:22 servername kernel: ovirtmgmt: port 1(enp2s0) entered forwarding state
Oct 23 23:13:22 servername kernel: ovirtmgmt: port 1(enp2s0) entered forwarding state
Oct 23 23:13:25 servername vdsmd_init_common.sh: libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-ovirtmgmt'
Oct 23 23:13:26 servername kernel: IPv6: ADDRCONF(NETDEV_UP): enp8s5f1: link is not ready
Oct 23 23:13:26 servername kernel: 8021q: adding VLAN 0 to HW filter on device enp8s5f1
Oct 23 23:13:26 servername kernel: e1000: enp8s5f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Oct 23 23:13:26 servername kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp8s5f1: link becomes ready
Oct 23 23:13:34 servername kernel: NETNAME10: port 1(enp8s5f0.10) entered forwarding state
Oct 23 23:13:34 servername kernel: NETNAME10: port 1(enp8s5f0.10) entered forwarding state
Oct 23 23:13:34 servername vdsmd_init_common.sh: libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-NETNAME10'
Oct 23 23:13:35 servername kernel: device enp8s5f0.131 entered promiscuous mode
Oct 23 23:13:35 servername kernel: NETNAME20: port 1(enp8s5f0.131) entered forwarding state
Oct 23 23:13:35 servername kernel: NETNAME20: port 1(enp8s5f0.131) entered forwarding state
Oct 23 23:13:35 servername vdsmd_init_common.sh: libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-NETNAME20'
Oct 23 23:13:42 servername kernel: bnx2 0000:06:00.0 enp6s0: using MSI
Oct 23 23:13:42 servername kernel: IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 23 23:13:42 servername kernel: device enp6s0 entered promiscuous mode
Oct 23 23:13:42 servername kernel: bnx2 0000:06:00.0 enp6s0: NIC SerDes Link is Up, 1000 Mbps full duplex
Oct 23 23:13:42 servername kernel:
Oct 23 23:13:42 servername kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready

This repeats and repeats.

Version-Release number of selected component (if applicable):

VDSM vdsm-4.16.7-1.gitdb83943.el7
Libvirt libvirt-1.1.1-29.el7_0.3
KVM 1.5.3 - 60.el7_0.2

How reproducible:

Install new host and setup networks


Steps to Reproduce:
1. Add new host
2. Setup networks, save them
3. Activate

Actual results:

Host unresponsable and disconnects on the network.

Expected results:

Activated Server

Additional info:

Comment 1 Dan Kenigsberg 2014-10-26 23:05:30 UTC

Please share the logs of ovirt-host-deploy, engine.log, vdsm.log and supervdsm.log.

The current subject of this bug is an annoying false error (bug 1121571) and not a helpful pointer to your issue.

I'm temporarily changing severity, as many deployments do succeed.

Comment 2 Yamakasi 2014-10-26 23:12:14 UTC

This seems to be solved at this moment.

I might could have been an issue with the installed packages, config, approving and reinstalling again.