Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APIv2: DELETE libpod/containers/foo?force=true: unlinkat: directory not empty #7535

Closed
edsantiago opened this issue Sep 2, 2020 · 4 comments · Fixed by #7662
Closed

APIv2: DELETE libpod/containers/foo?force=true: unlinkat: directory not empty #7535

edsantiago opened this issue Sep 2, 2020 · 4 comments · Fixed by #7662
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

Probable flake; filing so we can track it. In API tests:

ok 256 [25-containersMore] POST libpod/containers/foo/mount [] : status=200
ok 257 [25-containersMore] Check container mount ('/tmp/test-apiv2.tmp.QENVh1/overlay/7a4337c7d7df8e5d442d365fb12fc4feba80a722bf7775d1416acc001cfe92d2/merged') ~ .*merged
ok 258 [25-containersMore] POST libpod/containers/foo/unmount [] : status=204
not ok 259 [25-containersMore] DELETE libpod/containers/foo?force=true : status
#  expected: 204
#    actual: 500
  expected: 204
not ok 260 [25-containersMore] DELETE libpod/containers/foo?force=true: 204 status returns no output
#  expected: ''
#    actual: {"cause":"1 error occurred:
	* unlinkat /tmp/test-apiv2.tmp.QENVh1/overlay/7a4337c7d7df8e5d442d365fb12fc4feba80a722bf7775d1416acc001cfe92d2: directory not empty
         
","message":"error removing container 41d043ac3e04c3988f10f94be3b457fe2f79f058505ea7c0ad88ecaa0b6123d8 root filesystem: 1 error occurred:
	* unlinkat /tmp/test-apiv2.tmp.QENVh1/overlay/7a4337c7d7df8e5d442d365fb12fc4feba80a722bf7775d1416acc001cfe92d2: directory not empty
         
","response":500}
  expected: ''

Source: apiv2_test in #7534

Am assuming it's a flake, since I didn't touch any of this code. Will restart failing test.

@edsantiago edsantiago added flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. labels Sep 2, 2020
@vrothberg
Copy link
Member

Also seen here https://cirrus-ci.com/task/6597748277379072 in #6811

@vrothberg
Copy link
Member

vrothberg commented Sep 7, 2020

I've been poking around in the code and couldn't find anything suspicious in the code that would explain the flake.

However, local podman will evict containers in case of force which the remote one does not. Cc @baude @jwhonce.

Could it be that the unmount (right before the delete in the test) hasn't finished? @giuseppe WDYT?

@mheon
Copy link
Member

mheon commented Sep 8, 2020

My first suspicion would be that the unmount has not completely finished. If we add a 5-second sleep between them, that would help confirm the race.

@edsantiago
Copy link
Member Author

This one is quickly becoming the number-one flake

259 [25-containersMore] DELETE libpod/containers/foo?force=true : status

260 [25-containersMore] DELETE libpod/containers/foo?force=true: 204 status returns no output

jwhonce added a commit to jwhonce/podman that referenced this issue Sep 18, 2020
mheon pushed a commit to mheon/libpod that referenced this issue Sep 25, 2020
codemaker219 pushed a commit to bitsolve/podman that referenced this issue Jan 8, 2021
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants