Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
See the discussion at https://github.com/linux-system-roles/podman/pull/78 - specifically:

"Can you make it conditional on a podman command output podman info --format {{.Host.NetworkBackend}}?
If this says CNI you will need podman-plugins installed for dns, if it says netavark you need aardvark-dns installed (that should be default on RHEL 9 newer).

I think it is worth to file a bz against RHEL 8 and ask for a recommends on podman-plugins there. I am not aware of any reason why it should not be installed."

Note that the podman packages on RHEL9 and Fedora work without having to install additional dependencies - the RHEL8 package should also, by having a "Requires: podman-plugins"

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

This BZ will supersede https://bugzilla.redhat.com/show_bug.cgi?id=2218917 so I'm closing that as a duplicate.

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

This bug has been verified on podman-4.6.0-0.2 and podman-4.6.0-0.3.

[root@rhel-9 tmp]# rpm -qRi podman-4.6.0-0.2.module+el8.9.0+19303+8513fba8.x86_64.rpm |grep podman-plugins
podman-plugins >= 3:4.6.0-0.2.module+el8.9.0+19303+8513fba8

[root@rhel-9 tmp]# rpm -qRi podman-4.6.0-0.3.module+el8.9.0+19362+3c57b429.x86_64.rpm |grep podman-plugins
podman-plugins >= 3:4.6.0-0.3.module+el8.9.0+19362+3c57b429

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 and bug fix 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:6939