Bug 2116481

Summary:	Two aardvark-dns instances trying to use the same port on the same interface (netavark)
Product:	Red Hat Enterprise Linux 8	Reporter:	Arya Rajendran <arajendr>
Component:	netavark	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	Joy Pu <ypu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	bbaude, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, pgm-rhel-tools, pthomas, tsweeney, umohnani, ypu
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	8.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	netavark-1.2.0-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2130234 2130235 (view as bug list)		Environment:
Last Closed:	2023-05-16 08:20:33 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:
Bug Depends On:
Bug Blocks:	2130234, 2130235, 2136306, 2136395, 2136933

Description Arya Rajendran 2022-08-08 15:30:17 UTC

Description of problem:

aardvark-dns, two processes, trying to use the same port on the same interface

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

Rhel8.6

How reproducible:

Reproducible when using customer product on low power hardware.

Steps to Reproduce:

1. Create 20-30 containers with corresponding systemd .service file via podman generate systemd

2. Enable all these services so containers are brought up on reboot

3. Reboot

Actual results:

Observe 2 aardvark-dns processes running on the same bridge interface which is used by containers.

Expected results:

Only one aardvark-dns instances.

Comment 2 Tom Sweeney 2022-08-08 21:20:10 UTC

*** Bug 2116480 has been marked as a duplicate of this bug. ***

Comment 10 Brent Baude 2022-08-27 16:05:45 UTC

https://github.com/containers/netavark/pull/375

Comment 20 Tom Sweeney 2022-09-28 13:55:38 UTC

*** Bug 2130234 has been marked as a duplicate of this bug. ***

Comment 23 Tom Sweeney 2022-09-28 19:14:47 UTC

@mheon @bbaude Please see prior comment from Jindrich about the missing tarball.

Comment 27 Joy Pu 2022-11-08 13:29:12 UTC

Checked with aardvark-dns-1.2.0-1.module+el8.8.0+16777+b77867ec.x86_64 and netavark-1.2.0-1.module+el8.8.0+16777+b77867ec.x86_64. Start and stop 30 container service in the same time several times, no error triggered. Also checked the source code, the fix is verified by the customer and included in the build. So move it to verified.

Comment 29 errata-xmlrpc 2023-05-16 08:20:33 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 (Moderate: container-tools:rhel8 security, 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/RHSA-2023:2758

Comment 30 errata-xmlrpc 2023-05-16 08:39:24 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 (Moderate: container-tools:rhel8 security, 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/RHSA-2023:2758

Comment 31 Red Hat Bugzilla 2023-09-18 04:44:11 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days