Bug 1977673

Summary: podman v3.2.2 writes image events too early
Product: Red Hat Enterprise Linux 8 Reporter: Valentin Rothberg <vrothber>
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, ypu
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-3.2.3-0.4.el8 or newer Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 17:38:44 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 Valentin Rothberg 2021-06-30 09:13:35 UTC 
Description of problem:

Podman v3.2.2 (scheduled for RHEL 8.4.0.2) writes image events too early.  As reported upstream [1], the bug was detected running Podman's development branch against Cockpit tests.

The bug in questions points out that Podman writes an image-pull event before the image has actually been pulled.

[1] https://github.com/containers/podman/issues/10812


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

Podman v3.2.2.

How reproducible:

Always but hard to time since it's racy.

Additional info:

I already opened a PR against containers/common (https://github.com/containers/common/pull/655).  Once, we have ACKs I will create the backports and point the specific commit in Podman.
Comment 2 Valentin Rothberg 2021-07-01 14:00:22 UTC 
The fix [1] has been merged into v3.2 branch of Podman: https://github.com/containers/podman/tree/v3.2

Assigning to Jindrich to do the packaging magic.

[1] https://github.com/containers/podman/commit/6ecedc161804e84bf7454bbe147389680b4b8032
Comment 9 errata-xmlrpc 2021-11-09 17:38:44 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 (Moderate: 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-2021:4154