-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
e2e: podman system reset: unlinkat: directory not empty #17957
Comments
I do not see an immediate/obvious bug in the code. The |
I wonder if this could be related to #18057, tmpdir, podman-pause, namespaces? |
Good thinking! Let's see what happens once it has been resolved. |
A friendly reminder that this issue had no activity for 30 days. |
Funny you should mention it, github-bot! It failed again just today. Here are the two instances from the past month:
|
It's happening in ginkgov2, even with
|
Ha, that is interesting. Random guess: are we writing an event while trying to remove the directory? |
I instrumented the test, and just saw it trigger:
Does this help? |
Thanks, @edsantiago! Yes, I think that's helpful. Apologies, I am buried and don't have time to sniff into it at the moment. |
Another one, f38 root, exactly the same symptoms (events.log size 171, events.log.lock size 0). Would it help to |
|
Here's the list so far. I removed the
|
@edsantiago do you still see this flake? I am asking because of the recent storage fixes which may play a role. |
Last seen Sept 28 but this is an elusive one, infrequent, so I prefer not to close this yet.
Seen in: int podman fedora-38+fedora-39 rootless host boltdb+sqlite |
New failure just now in rawhide rootless:
Message is completely different -- "lock file ENOENT" instead of "unlinkat ENOTEMPTY" -- but I bet it's the same thing. |
...and we're back to |
The story so far
|
Still happening, on main, even after the system-reset work. rawhide rootless. Could this be related to the new panic, #21279? |
Ping, still happening
|
Still happening
|
podman system reset [It] podman system reset
The text was updated successfully, but these errors were encountered: