podman auto-update/system df: fix ErrNoSuchCtr/Volume race

[Luap99]

If a container is removed during the loop we should just ignore it. No
reason to log this as error to the user.

Fixes #23279

Does this PR introduce a user-facing change?

Fixed a race in podman auto-update and podman system df that would cause them to fail with an error if a container was removed at the same time.

[Luap99]

@edsantiago PTAL
That should help the parallel PR.

[Luap99]

/hold cancel

[edsantiago]

LGTM. @containers/podman-maintainers PTAL

[giuseppe]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edsantiago, giuseppe, Luap99

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Luap99,edsantiago,giuseppe]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[edsantiago]

Ugh, just saw this in one of my laptop parallel runs (in the 610 test):

   [05:55:38.197225634] $ /home/esm/src/atomic/2018-02.podman/libpod/bin/podman system df --format {{"\n"}}                                                     
   [05:55:38.297883560] Error: Image 5e5299c48745 exists in local storage but may be corrupted (remove the image to resolve the issue): reading image "5e5299c48
745fd521eedc49358c97e9e8bacfae02c7110e270fad05eaa6d7a05": locating image with ID "5e5299c48745fd521eedc49358c97e9e8bacfae02c7110e270fad05eaa6d7a05": image not k
nown                                                                                                                                                            
   [05:55:38.301820892] [ rc=125 ]

Any connection to this PR?

[Luap99]

no (I only touched container/volume code) the image query code is in libimage (c/common). It is is possible that it has a similar issue there