Bug 2052465

Summary:	[NMCI] ovs_mtu test fail
Product:	Red Hat Enterprise Linux 8	Reporter:	Vladimir Benes <vbenes>
Component:	NetworkManager	Assignee:	Lubomir Rintel <lrintel>
Status:	CLOSED ERRATA	QA Contact:	Vladimir Benes <vbenes>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bgalvani, ferferna, fge, lrintel, rkhan, sukulkar, till
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.36.0-1.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-10 14:55:01 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 Vladimir Benes 2022-02-09 10:37:38 UTC

Description of problem:
https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-main-veth-rhel8-upstream/916/artifact/artifacts/FAIL_report_NetworkManager-ci_Test0769_ovs_mtu.html (in attachment too for availability)

it seems it doesn't go up properly after the simulated reboot step.

Version-Release number of selected component (if applicable):
1.37.0-29670.copr.e23ebe9183.el8

How reproducible:
not sure

Steps to Reproduce:
1. run the ovs_mtu test in NMCI


Actual results:
activation error

Expected results:


Additional info:

Comment 3 Gris Ge 2022-02-24 06:39:09 UTC

The fix is merged. 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1117

Comment 6 Vladimir Benes 2022-02-28 17:04:42 UTC

working well in NMCI

Comment 8 errata-xmlrpc 2022-05-10 14:55:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2022:1985