Skip to content

podman stop, after kube play: Storage for container xxx has been removed #19702

@edsantiago

Description

@edsantiago

Seeing this often when I cherrypick #18442

...podman kube something
...test passes, then we get to AfterEach:
# podman [options] stop --all -t 0
           time="2023-08-22T07:11:18-05:00" level=error msg="Storage for container 5ec989fdc4954fe14c74f4e34345a34aeec61a0e2ee518219b01fa06e0445fca has been removed"
           59ded94ff300dd69bf0199a8f360cc1ac5a5262b03ccd34458407b421a765013
           4d93d65b97916b0b650c4ff50e4a1f1a8a4c657780c07a4a7546b7a96fc0b125
           5ec989fdc4954fe14c74f4e34345a34aeec61a0e2ee518219b01fa06e0445fca

FAIL expected no stderr

e.g. f38 root. Twice.

Metadata

Metadata

Assignees

No one assigned

    Labels

    flakesFlakes from Continuous Integrationlocked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions