Bug 1212825

Summary:	Race condition in docker/podman stop
Product:	[SUSE Linux Enterprise Server] PUBLIC SUSE Linux Enterprise Server 15 SP3	Reporter:	Ricardo Branco <rbranco>
Component:	Containers	Assignee:	Danish Prakash <danish.prakash>
Status:	IN_PROGRESS ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	danish.prakash, dcermak, felix.niederwanger, jalausuch, rbranco
Version:	SLES15SP3Maint-Upd	Flags:	dcermak: needinfo? (rbranco)
Target Milestone:	unspecified
Hardware:	Other
OS:	Other
URL:	https://openqa.suse.de/tests/11383574/modules/podman_network_cni/steps/142
Whiteboard:
Found By:	openQA	Services Priority:
Business Priority:		Blocker:	Yes
Marketing QA Status:	---	IT Deployment:	---

Description Ricardo Branco 2023-06-28 19:43:49 UTC

Details in upstream bug:
https://github.com/containers/podman/issues/19038

## Observation

openQA test in scenario sle-15-SP3-EC2-CHOST-BYOS-Updates-x86_64-publiccloud_containers@64bit fails in
[podman_network_cni](https://openqa.suse.de/tests/11383574/modules/podman_network_cni/steps/142)

## Test suite description
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.


## Reproducible

Fails since (at least) Build [20230618-1](https://openqa.suse.de/tests/11383574) (current job)


## Expected result

Last good: [20230617-1](https://openqa.suse.de/tests/11378055) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=EC2-CHOST-BYOS-Updates&machine=64bit&test=publiccloud_containers&version=15-SP3)

Comment 1 Dan Čermák 2023-09-26 09:49:46 UTC

I would suggest to change the code from `xargs podman stop` to `xargs podman rm -f` as that will circumvent the inherent TOCTU. Sadly, we were not able to find a way how to fix this inherent podman issue.

Comment 2 Felix Niederwanger 2024-03-27 12:31:42 UTC

Update: We see the same issue with docker on 15-SP4 now: https://openqa.suse.de/tests/13886270#step/docker/133

> docker stop CONTAINER
> docker ps
> ... shows the CONTAINER still in status UP

Comment 3 Felix Niederwanger 2024-05-22 10:49:53 UTC

For the record: We see this issue also on 15-SP6: https://openqa.suse.de/tests/14413815#step/docker/176