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.
Bug 2086757 - Error: plugin type="bridge" failed (add): failed to find plugin "bridge" in path
Summary: Error: plugin type="bridge" failed (add): failed to find plugin "bridge" in path
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: 8.7
Assignee: Jindrich Novy
QA Contact: Joy Pu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-16 14:38 UTC by Martin Pitt
Modified: 2022-11-08 09:32 UTC (History)
10 users (show)

Fixed In Version: podman-4.1.0-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:15:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-122201 0 None None None 2022-05-16 14:57:55 UTC
Red Hat Product Errata RHSA-2022:7457 0 None None None 2022-11-08 09:16:27 UTC

Description Martin Pitt 2022-05-16 14:38:11 UTC
Description of problem: Current RHEL 8.7 cannot start any containers.


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


podman-catatonit-4.1.0-2.module+el8.7.0+15223+3987d347.x86_64
podman-4.1.0-2.module+el8.7.0+15223+3987d347.x86_64
container-selinux-2.183.0-1.module+el8.7.0+15223+3987d347.noarch
containers-common-1-28.module+el8.7.0+15223+3987d347.x86_64
runc-1.0.3-6.module+el8.7.0+15223+3987d347.x86_64
package crun is not installed

How reproducible: Always


Steps to Reproduce:
1. podman run -it --rm docker.io/busybox

Actual results:

WARN[0003] Failed to load cached network config: network podman not found in CNI cache, falling back to loading network podman from disk 
WARN[0003] 1 error occurred:
                            	* plugin type="tuning" failed (delete): failed to find plugin "tuning" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin]
                                                           
Error: plugin type="bridge" failed (add): failed to find plugin "bridge" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin]


Expected results: container run works

Comment 1 Matthew Heon 2022-05-16 15:12:12 UTC
Can you verify if `containernetworking-cni` or `netavark` are installed?

Comment 2 Martin Pitt 2022-05-16 17:22:28 UTC
Sure!

package containernetworking-cni is not installed
netavark-1.0.1-28.module+el8.7.0+15223+3987d347.x86_64

netavark is a Requires: from podman. I installed containernetworking-cni, and that fixes the problem.

Comment 4 Matthew Heon 2022-05-17 16:01:38 UTC
We should be requiring one of CNI or Netavark, with CNI being recommended (on 8.x; 9.x will recommend Netavark). It looks like we're requiring netavark, probably on both 8 and 9, instead.

Comment 5 Tom Sweeney 2022-05-17 19:35:54 UTC
@jnovy can you verify what is and is not being required in 8.6/9.0 as noted by Matt in his last comment please?

Comment 6 Jindrich Novy 2022-05-18 07:54:20 UTC
Confirming, this is now fixed in the RHEL8.7 spec file.

Can we get qa ack please?

Comment 10 Joy Pu 2022-05-26 09:36:36 UTC
Checked with podman-4.1.0-3.module+el8.7.0+15410+5e301811.x86_64.rpm and the containernetworking-plugins is already added to the requires list. So move this to verified:
[root@dell-per430-27 ~]# yum deplist podman-4.1.0-3.module+el8.7.0+15410+5e301811.x86_64.rpm |grep network
Last metadata expiration check: 1:51:01 ago on Thu 26 May 2022 03:44:23 AM EDT.
  dependency: containernetworking-plugins >= 0.9.1-1
   provider: containernetworking-plugins-1:1.1.1-3.module+el8.7.0+15271+4011683a.x86_64

Comment 12 errata-xmlrpc 2022-11-08 09:15:47 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-2022:7457


Note You need to log in before you can comment on or make changes to this bug.