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:
When running a container via podman, the following errors are logged to dmesg and pop up on the console:
[ 30.648852] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 30.662142] IPv6: ADDRCONF(NETDEV_CHANGE): vethd6d8e018: link becomes ready
[ 30.662202] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 30.662447] cni-podman0: port 1(vethd6d8e018) entered blocking state
[ 30.662470] cni-podman0: port 1(vethd6d8e018) entered disabled state
[ 30.662535] device vethd6d8e018 entered promiscuous mode
[ 30.662612] cni-podman0: port 1(vethd6d8e018) entered blocking state
[ 30.662633] cni-podman0: port 1(vethd6d8e018) entered forwarding state
[ 30.683316] Warning: Deprecated Driver is detected: nft_compat will not be maintained in a future major release and may be disabled
[ 36.217706] cni-podman0: port 1(vethd6d8e018) entered disabled state
[ 36.217967] device vethd6d8e018 left promiscuous mode
[ 36.217984] cni-podman0: port 1(vethd6d8e018) entered disabled state
[root@localhost ~]#
Version-Release number of selected component (if applicable):
podman-4.0.2-6.el9_0.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install RHEL 9 and podman
2. Run a container
3. Check dmesg for the deprecated messages
Actual results:
Things work fine, but using deprecated functionality
Expected results:
Latest podman uses fully supported functionality
Additional info:
After removing podman from this VM and removing /var/lib/containers/* and reinstalling, I now have the z-stream fix that pulls in netavark. The CNI message sare gone, but there's still the deprecated bridge filtering and nft_compt module messages when running a container:
[May27 15:18] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ +0.017111] podman0: port 1(veth710ff9ff) entered blocking state
[ +0.000031] podman0: port 1(veth710ff9ff) entered disabled state
[ +0.000053] device veth710ff9ff entered promiscuous mode
[ +0.003681] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ +0.000046] IPv6: ADDRCONF(NETDEV_CHANGE): veth710ff9ff: link becomes ready
[ +0.000036] podman0: port 1(veth710ff9ff) entered blocking state
[ +0.000025] podman0: port 1(veth710ff9ff) entered forwarding state
[ +0.022233] Warning: Deprecated Driver is detected: nft_compat will not be maintained in a future major release and may be disabled
[ +2.433978] podman0: port 1(veth710ff9ff) entered disabled state
[ +0.000328] device veth710ff9ff left promiscuous mode
[ +0.000018] podman0: port 1(veth710ff9ff) entered disabled state
[root@localhost ~]# rpm -q podman
podman-4.0.2-7.el9_0.x86_64
[root@localhost ~]#
Comment 7RHEL Program Management
2023-09-11 18:32:58 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8RHEL Program Management
2023-09-11 18:38:01 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.