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 2005972 - podman 3.2.3: Recovering from API handler panic: runtime error: index out of range [58] with length 58, goroutine 805 [running]
Summary: podman 3.2.3: Recovering from API handler panic: runtime error: index out of ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Edward Shen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-20 15:13 UTC by arottigni
Modified: 2022-05-10 13:45 UTC (History)
11 users (show)

Fixed In Version: podman-4.0.0-0.9.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 13:27:52 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-97767 0 None None None 2021-09-21 15:31:14 UTC
Red Hat Product Errata RHSA-2022:1762 0 None None None 2022-05-10 13:28:16 UTC

Description arottigni 2021-09-20 15:13:42 UTC
Description of problem:
Creating and removing containers frequently using the podman's sometimes fails with the following error:
Recovering from API handler panic: runtime error: index out of range [58] with length 58, goroutine 805 [running]

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

How reproducible:

Sometimes (depending on the system because it is a race condition)

1. Steps to Reproduce:
2.Create a container using the REST api
3. Start the container
4. Wait on the container
5. Remove the container
6. go to step 1

Actual results:
It fails sometimes when you try to create a container: Recovering from API handler panic: runtime error: index out of range [58] with length 58, goroutine 805 [running]

Expected results:
The container should be created successfully.

Additional info:
Upstream issues: https://github.com/containers/podman/issues/11487
Upstream PR to fix main branch: https://github.com/containers/storage/pull/1014

It would be great if the upstream fix can be backported to v3.3.

Comment 13 errata-xmlrpc 2022-05-10 13:27:52 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 (Important: 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:1762


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