RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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. podman starts first container, checks if there's aardvark-dns process running .
2. As there is no aardvark-dns instances running it starts it
3. aardvark-dns initializes and writes it's PID to pidfile
4. Another container is being started in parallel with the first one, so podman performs aardvark-dns checks
5. As first aardvark-dns hasn't finished initializing yet it haven't wrote its PID to pidfile
6. Second container assumes there's no aardvark-dns running due to an empty pidfile
7. Attempts to start it
8. We now have two aardvark-dns instances, one (the first one), bound to port 53 (as it was able to do it because it started and requested it first), second overwriting pidfile with its PID (unable to bind as port is already in use).
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.

I'm closing this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2116481.  If I'm mistaken and this is not a dupe, please reopen and add a comment with clarification please.

*** This bug has been marked as a duplicate of bug 2116481 ***

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