Interrupting a podman pod rm -f PODNAME corrupts pod/container database

[pohlt]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Interrupting a podman pod rm -f PODNAME (e.g. with CTRL+C) leaves containers and pod in an inconsistent state.
Containers can be removed, but trying to remove the pod itself fails:

> podman pod ps
POD ID        NAME              STATUS      CREATED     INFRA ID      # OF CONTAINERS
aaf585be9cc3  singtundschwingt  Error       4 days ago  ae4ff069f320  1

> podman ps -a
CONTAINER ID  IMAGE                                    COMMAND     CREATED     STATUS      PORTS       NAMES
ae4ff069f320  localhost/podman-pause:4.2.0-1660228937              4 days ago  Removing                aaf585be9cc3-infra

> podman pod rm singtundschwingt 
Error: error freeing lock for container ae4ff069f3200db700dbffea790731e41e9b8eaa29916f2434d4df9b79c0914c: no such file or directory

Probably similar root cause as #15526?

Steps to reproduce the issue:

1. Create any pod (ours had about ten containers).

2. Interrupt a podman pod rm -f PODNAME using CTRL+C.

Describe the results you received:

Chances are that you now have an un-removable pod.

Describe the results you expected:

Pod and containers are removed successfully.

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Client:       Podman Engine
Version:      4.2.0
API Version:  4.2.0
Go Version:   go1.18.4
Built:        Thu Aug 11 16:42:17 2022
OS/Arch:      linux/amd64

Output of podman info:

host:
  arch: amd64
  buildahVersion: 1.27.0
  cgroupControllers:
  - cpu
  - io
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.0-2.fc36.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.0, commit: '
  cpuUtilization:
    idlePercent: 76.37
    systemPercent: 4.49
    userPercent: 19.14
  cpus: 8
  distribution:
    distribution: fedora
    variant: kde
    version: "36"
  eventLogger: journald
  hostname: slim
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.19.6-200.fc36.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree: 1916342272
  memTotal: 16503115776
  networkBackend: cni
  ociRuntime:
    name: crun
    package: crun-1.5-1.fc36.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.5
      commit: 54ebb8ca8bf7e6ddae2eb919f5b82d1d96863dea
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.0-0.2.beta.0.fc36.x86_64
    version: |-
      slirp4netns version 1.2.0-beta.0
      commit: 477db14a24ff1a3de3a705e51ca2c4c1fe3dda64
      libslirp: 4.6.1
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.3
  swapFree: 8312102912
  swapTotal: 8589930496
  uptime: 39h 59m 9.00s (Approximately 1.62 days)
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  configFile: /home/tom/.config/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 0
    stopped: 1
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/tom/.local/share/containers/storage
  graphRootAllocated: 498387124224
  graphRootUsed: 59129524224
  graphStatus:
    Backing Filesystem: btrfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 78
  runRoot: /run/user/1000/containers
  volumePath: /home/tom/.local/share/containers/storage/volumes
version:
  APIVersion: 4.2.0
  Built: 1660228937
  BuiltTime: Thu Aug 11 16:42:17 2022
  GitCommit: ""
  GoVersion: go1.18.4
  Os: linux
  OsArch: linux/amd64
  Version: 4.2.0

Package info (e.g. output of rpm -q podman or apt list podman):

podman-4.2.0-2.fc36.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):

local machine w/o any virtualization

[baude]

@mheon i think this is probably up your alley.

[mheon]

Almost certainly the same issue as #15526 - going to close as such. Fix coming soon.