Bug 1671739

Summary:

VMs with external networks cannot boot-up after Upgrade from 4.2.7.1 to 4.2.8

Product:

[oVirt] ovirt-engine

Reporter:

ada <adaper3>

Component:

BLL.Network

Assignee:

Dan Kenigsberg <danken>

Status:

CLOSED DUPLICATE

QA Contact:

Michael Burman <mburman>

Severity:

urgent

Docs Contact:

Priority:

unspecified

Version:

4.2.4.5

CC:

adaper3, bugs, dholler

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

All

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2019-02-14 12:22:27 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
vdsm_log	none
engine_log	none

Description ada 2019-02-01 13:51:28 UTC

Description of problem:

After upgrading my hosts from 4.2.7.1 to 4.2.8 the external networks
stopped working.
When im starting a VM using external network it does not boot up at all.

The error message is:
"VM is down with error. Exit message: unsupported configuration: filterref
is not supported for network interfaces with virtualport type openvswitch"

I rolled it back to 4.2.7.1 for 1 of my hosts just as a test and the VMs on
that host can now bootup using external networks as they are supposed to!

Please advice as i would like to use the upgrade.

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


How reproducible:


Steps to Reproduce:
1.Upgrade hosts from 4.2.7.1 to 4.2.8
2.Create an external network with external provider: ovirt-provider-ovn 
3. Add the external network to the VM NIC. 
4.Start the VM

Actual results: VM does not boot


Expected results: VM to boot up

Comment 1 Dominik Holler 2019-02-05 08:10:51 UTC

Can you please share the vdsm.log from a host and the engine.log after a failed start?

Comment 2 ada 2019-02-07 07:42:53 UTC

Created attachment 1527770 [details]
vdsm_log

Comment 3 ada 2019-02-07 07:43:27 UTC

Created attachment 1527771 [details]
engine_log

Comment 4 ada 2019-02-07 07:46:21 UTC

(In reply to Dominik Holler from comment #1)
> Can you please share the vdsm.log from a host and the engine.log after a
> failed start?

Please find the logs attached.
As it turns out even the newly created networks under 4.2.8 have the filter.


Thanks

Comment 5 Dominik Holler 2019-02-07 08:15:51 UTC

(In reply to ada from comment #4)
> (In reply to Dominik Holler from comment #1)
> > Can you please share the vdsm.log from a host and the engine.log after a
> > failed start?
> 
> Please find the logs attached.

Thanks for sharing the logs.

> As it turns out even the newly created networks under 4.2.8 have the filter.
> 

oVirt's linux bridge based networks should be created with a filter, but not
external networks, which are created on an external provider.

Can you please check, if the default setting for newly created external networks
on the ovirt-provider-ovn have filter by default?
If so, can you please explain how you created the network, e.g. by REST-API or
web UI?

Comment 6 Michael Burman 2019-02-07 08:59:43 UTC

QE can't reproduce the report on 4.2.8.3-0.1.el7ev
The origin bug was fixed in 4.2.6, see BZ 1601469

Comment 7 ada 2019-02-08 12:53:03 UTC

(In reply to Dominik Holler from comment #5)
> (In reply to ada from comment #4)
> > (In reply to Dominik Holler from comment #1)
> > > Can you please share the vdsm.log from a host and the engine.log after a
> > > failed start?
> > 
> > Please find the logs attached.
> 
> Thanks for sharing the logs.
> 
> > As it turns out even the newly created networks under 4.2.8 have the filter.
> > 
> 
> oVirt's linux bridge based networks should be created with a filter, but not
> external networks, which are created on an external provider.
> 
> Can you please check, if the default setting for newly created external
> networks
> on the ovirt-provider-ovn have filter by default?
> If so, can you please explain how you created the network, e.g. by REST-API
> or
> web UI?


When i am creating the ext network from WEB UI the filters are there by default.

When i am creating teh networks from the API no filtering occurs.

Comment 8 ada 2019-02-08 12:58:54 UTC

(In reply to Michael Burman from comment #6)
> QE can't reproduce the report on 4.2.8.3-0.1.el7ev
> The origin bug was fixed in 4.2.6, see BZ 1601469


i am using oVirt Node 4.2.8.
NETWORKS/NETWORKS/NEW ->create on external provider checked

and the network created comes with vdsm-no-mac-spoofing

Comment 9 Dominik Holler 2019-02-12 07:53:19 UTC

(In reply to ada from comment #8)
> (In reply to Michael Burman from comment #6)
> > QE can't reproduce the report on 4.2.8.3-0.1.el7ev
> > The origin bug was fixed in 4.2.6, see BZ 1601469
> 
> 
> i am using oVirt Node 4.2.8.
> NETWORKS/NETWORKS/NEW ->create on external provider checked
> 
> and the network created comes with vdsm-no-mac-spoofing

Thanks for checking this.
What is the version of ovirt-engine you are using?

Comment 10 ada 2019-02-14 09:01:33 UTC

Please see below all the info retrieved from a node:


OS Version:
RHEL - 7 - 6.1810.2.el7.centos
OS Description:
oVirt Node 4.2.8
Kernel Version:
3.10.0 - 957.1.3.el7.x86_64
KVM Version:
2.12.0 - 18.el7_6.1.1
LIBVIRT Version:
libvirt-4.5.0-10.el7_6.3
VDSM Version:
vdsm-4.20.46-1.el7
SPICE Version:
0.14.0 - 6.el7
GlusterFS Version:
glusterfs-3.12.15-1.el7
CEPH Version:
librbd1-10.2.5-4.el7
Kernel Features:
PTI: 1, IBRS: 0, RETP: 1

Comment 11 ada 2019-02-14 12:12:25 UTC

version is: 4.2.4.5-1.el7

Comment 12 Dominik Holler 2019-02-14 12:22:27 UTC

(In reply to ada from comment #11)
> version is: 4.2.4.5-1.el7

Thank you for sharing this.
The origin bug was fixed in 4.2.6, see BZ 1601469 .
So updating ovirt-engine should solve the issue for you.

*** This bug has been marked as a duplicate of bug 1601469 ***