Bug 1217828

Summary:	podman not using netavark as default
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Felix Niederwanger <felix.niederwanger>
Component:	Containers	Assignee:	Containers Team <containers-bugowner>
Status:	NEW ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	bruno.leon, dominik.gedon, rbranco
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Felix Niederwanger 2023-12-05 16:15:43 UTC

On Tumbleweed, despite being on podman 4.8.0 we are still using CNI instead of netavark as the default network backend

https://openqa.opensuse.org/tests/3781263#step/podman/48

This issue was detected while extending the podman tests on Tumbleweed.

Comment 1 Bruno Leon 2023-12-06 07:54:14 UTC

If I remember correctly you need to install the netavark package first to have Podman use it.

If you install Podman first, it uses and stick to CNI unless you force it in the conf/reset it.

Comment 2 Felix Niederwanger 2023-12-06 14:54:09 UTC

Hey Bruno. Yes and this is the issue. As of now we should have switched to netavark by default on new Tumbleweed/MicroOS installations.

This ticket does not address any migration plans for existing installation. But new ones should have netavark.

See https://suse.slack.com/archives/C02DR0C5XUY/p1701764573199999

Comment 4 Maintenance Automation 2024-02-07 12:30:08 UTC

SUSE-RU-2024:0408-1: An update that has one fix can now be installed.

Category: recommended (moderate)
Bug References: 1217828
Sources used:
openSUSE Leap 15.5 (src): podman-4.8.3-150500.3.6.1
SUSE Linux Enterprise Micro 5.5 (src): podman-4.8.3-150500.3.6.1
Containers Module 15-SP5 (src): podman-4.8.3-150500.3.6.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

Comment 8 Ricardo Branco 2024-05-06 10:34:35 UTC

I'm seeing this bug on SLEM 5.5.