podman info fails while removing container

[chrmarti]

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

/kind bug

Description

podman info fails while removing container.

Steps to reproduce the issue:

1. Run:

podman rm -f `podman run -d debian sleep infinity` & ; sleep 3 ; podman info

Describe the results you received:

~ podman rm -f `podman run -d debian sleep infinity` & ; sleep 3 ; podman info
[1] 12578
c80577d1546fb9bb6560d60d46000349038b650eccde4d4adb4e8a09a694af66
[1]  + 12578 done       podman rm -f `podman run -d debian sleep infinity`
Error: error getting info: error getting store info: container c80577d1546fb9bb6560d60d46000349038b650eccde4d4adb4e8a09a694af66 does not exist in database: no such container
~ echo $?
125

Describe the results you expected:

podman info should print the info either including or excluding the container being removed, but not fail.

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

Output of podman version:

Version:            1.9.1
RemoteAPI Version:  1
Go Version:         go1.12.10
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  gitCommit: ""
  goVersion: go1.12.10
  podmanVersion: 1.9.1
host:
  arch: amd64
  buildahVersion: 1.14.8
  cgroupVersion: v1
  conmon:
    package: 'conmon: /usr/libexec/podman/conmon'
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.15, commit: '
  cpus: 4
  distribution:
    distribution: ubuntu
    version: "19.10"
  eventLogger: file
  hostname: chrmarti-ubuntu
  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.3.0-51-generic
  memFree: 4620906496
  memTotal: 8342278144
  ociRuntime:
    name: runc
    package: 'cri-o-runc: /usr/lib/cri-o-runc/sbin/runc'
    path: /usr/lib/cri-o-runc/sbin/runc
    version: 'runc version spec: 1.0.1-dev'
  os: linux
  rootless: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: 'slirp4netns: /usr/bin/slirp4netns'
    version: |-
      slirp4netns version 1.0.0
      commit: unknown
      libslirp: 4.2.0
  swapFree: 2147479552
  swapTotal: 2147479552
  uptime: 21m 2.23s
registries:
  search:
  - docker.io
  - quay.io
store:
  configFile: /home/chrmarti/.config/containers/storage.conf
  containerStore:
    number: 2
    paused: 0
    running: 0
    stopped: 2
  graphDriverName: vfs
  graphOptions: {}
  graphRoot: /home/chrmarti/.local/share/containers/storage
  graphStatus: {}
  imageStore:
    number: 6
  runRoot: /run/user/1000/containers
  volumePath: /home/chrmarti/.local/share/containers/storage/volumes

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

podman/unknown,now 1.9.1~1 amd64 [installed]
podman/unknown 1.9.1~1 arm64
podman/unknown 1.9.1~1 armhf

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

Ubuntu 19.10 VM on Parallels for Mac.

[davidstrauss]

Is the change in #116 sufficient to fix this issue? Can this also be closed?

The mention in #2882 points to this as an upstream issue, so I'm not aware of other pending work that should be necessary to closing this.

[chrmarti]

#6091 sounds like it might address it. I can give it a try when it is released.

[rhatdan]

Yes that is the goal, it is fixed in master.