Bug 2105171

Summary:	"podman manifest add" is not concurrent safe
Product:	Red Hat Enterprise Linux 9	Reporter:	Suhaas Bhat <subhat>
Component:	podman	Assignee:	Tom Sweeney <tsweeney>
Status:	CLOSED CURRENTRELEASE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	bbaude, dwalsh, jnovy, lsm5, mheon, pthomas, umohnani
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-04 20:13:30 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 Suhaas Bhat 2022-07-08 08:01:22 UTC

Description of problem:
 If we try to add different images to the same manifest in parallel, sometimes one images is "lost".

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

How reproducible:
100%

Steps to Reproduce:
https://github.com/containers/podman/issues/14667

Actual results:
Manifests are created with "random" number of images.

Expected results:
Manifest should always contain 2 images.

Additional info:
As per the request has been made to be included this in podman 4.1 release.

Comment 1 Tom Sweeney 2023-05-04 20:13:30 UTC

Fixed in July 2022 with https://github.com/containers/common/pull/1090  Should be fixed in Podman v4.2 and above.