Bug 2005972

Summary: podman 3.2.3: Recovering from API handler panic: runtime error: index out of range [58] with length 58, goroutine 805 [running]
Product: Red Hat Enterprise Linux 8 Reporter: arottigni
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Edward Shen <weshen>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.4CC: bbaude, dwalsh, jligon, jnovy, lsm5, mheon, pthomas, tsweeney, umohnani, vrothber, ypu
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: podman-4.0.0-0.9.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-10 13:27:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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