This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2143282 - podman from 9.1 cannot start a container when installed on RHEL 9.0
Summary: podman from 9.1 cannot start a container when installed on RHEL 9.0
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: crun
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Giuseppe Scrivano
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-16 14:26 UTC by Ondřej Budai
Modified: 2023-09-11 19:06 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-11 19:06:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
all packages on the system (12.89 KB, text/plain)
2022-11-16 14:26 UTC, Ondřej Budai
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-3104 0 None Migrated None 2023-09-11 19:06:50 UTC
Red Hat Issue Tracker RHELPLAN-139642 0 None None None 2022-11-16 15:26:48 UTC

Description Ondřej Budai 2022-11-16 14:26:59 UTC
Created attachment 1924710 [details]
all packages on the system

Description of problem:
We are using quite an old RHEL 9.0 image. Since 9.1 was released, we began to see the following message when we install podman there and run podman run -it --rm ubi8 bash (both rootful and rootless):

/usr/bin/crun: symbol lookup error: /usr/bin/crun: undefined symbol: criu_feature_check
ERRO[0008] Removing container 78466eb964523e69916ef96289126ee971f1aed795b957b5738e256d46742d69 from runtime after creation failed 
Error: OCI runtime error: crun: /usr/bin/crun: symbol lookup error: /usr/bin/crun: undefined symbol: criu_feature_check

Version-Release number of selected component (if applicable):
podman-4.2.0-7.el9_1.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install RHEL 9.0 GA and subscribe
2. dnf install -y podman
3. podman run -it --rm ubi8 bash

Actual results:
/usr/bin/crun: symbol lookup error: /usr/bin/crun: undefined symbol: criu_feature_check
ERRO[0010] Removing container bfa6142606da0b33dec26f1def21847215519860f4040c542c7c1e2591286f08 from runtime after creation failed 
Error: OCI runtime error: crun: /usr/bin/crun: symbol lookup error: /usr/bin/crun: undefined symbol: criu_feature_check

Expected results:
I get bash in a container

Comment 5 RHEL Program Management 2023-09-11 19:03:57 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 6 RHEL Program Management 2023-09-11 19:06:51 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.


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