Bug 2112255

Summary:	[RFE] Podman (netavark backend) tears down bridge on last container shutdown
Product:	Red Hat Enterprise Linux 8	Reporter:	Arya Rajendran <arajendr>
Component:	podman	Assignee:	Brent Baude <bbaude>
Status:	ASSIGNED ---	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	bbaude, cpippin, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, mrussell, pholzing, pthomas, tsweeney, umohnani
Target Milestone:	rc	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	---	Flags:	dornelas: needinfo? (arajendr) bbaude: needinfo? (arajendr) tsweeney: needinfo? (bbaude) tsweeney: needinfo? (mrussell)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-05 15:22:38 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Arya Rajendran 2022-07-29 07:25:27 UTC

Description of problem:

If last container using given bridge stops, podman tears it down. 

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

RHEL 8.6
Podman

How reproducible:

Always

Steps to Reproduce:
1. Containers are started during boot, using legacy network-scripts functionality.
2. Also run few services which we bind to the IP address of bridge.
3. When OS boots up, bridges are brought up, services started and bound to ipaddress.
4. Then we run containers which also use same bridge
5. It works just fine
6. But, If last container using given bridge stops, podman tears it down
7. This leaves OS without bridge that few services depend on.
8. Bridge itself is recreated by podman when new container using this bridge starts


Actual results:

Podman (netavark backend) tears down bridge on last container shutdown.

Expected results:

The bridge should not be affected by the fact that no containers are using it anymore.