Bug 2226810

Summary:	Update Netavark to upstream
Product:	Red Hat Enterprise Linux 9	Reporter:	ivanov17 <ivanov17>
Component:	netavark	Assignee:	Jindrich Novy <jnovy>
Status:	NEW ---	QA Contact:	David Darrah/Red Hat QE <ddarrah>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, ivanov17, jwboyer
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 ivanov17 2023-07-26 15:57:34 UTC

Description of problem:

With Netavark 1.5.0 I have the same bug as in https://github.com/containers/netavark/issues/636

This bug was fixed with https://github.com/containers/netavark/pull/638
and the fix was added in release 1.6.0: https://github.com/containers/netavark/commits/v1.6.0

CentOS 9 Stream has newer version of Podman than latest Fedora release, but at the same time has an older version of Netavark.

Please, update the Netavark package for CentOS 9 Stream.

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

# /usr/libexec/podman/netavark --version
netavark 1.5.0

# podman --version
podman version 4.6.0-rc2

How reproducible: always

Steps to Reproduce: 

# dnf info netavark

Actual results:

Netavark version is 1.5.0

Expected results:

Netavark version is at least 1.6.0