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.

One curious thing that we have noticed is that gnome-shell is running. Is this a server or a desktop?

Hi Mike would it be possible to get access to the node where this issue is occurring?

Hi Urvashi,

I could ask the support engineer to set up a remote session, and we could ask them to execute commands in their environment, and we could observe the results. What is your availability today for that?

Mike

Hi Mike, would 4pm EST today work?

We've identified 2 back ports likely to fix the issues here:

https://github.com/containerd/containerd/pull/872/commits/de0e943db45b57fe2d422a6d1ebdffd5005a5296
https://github.com/containerd/containerd/pull/828/commits/6feebe941995c6086e9bfbe5c88834e90c7f43e4

we are back porting these as we speak, we'll have a test build for customer who are willing to test the package.

If it turns out that it's actually fixing the issue, we can go with an hotfix package.

Lokesh, I'll ask you to rebuild docker once we have back ports in place.

We've rebuilding docker with an additional BZ fixed that could help with this whole issue (https://bugzilla.redhat.com/show_bug.cgi?id=1636259)

we've rebuilding the docker package again.

That panic has already been fixed by https://github.com/projectatomic/containerd/commit/8c0b404ff7eaae3cfd47b5517470e736f6d52bd6

docker-1.13.1-75.git8633870.el7_5.x86_64 <- this package is old at this point also, we've rebuilt docker with the fixes in question again.

This is actually a docker bug and affects any version of OpenShift using docker 1.13.1 (OCP 3.9, 3.10, 3.11)