Only check for PodStateExited when pruning pods

[rhatdan]

[NO TESTS NEEDED] This is an attempt to fix a Race condition
since it is a race it is difficult to fix test.

Helps fix: #7139

Signed-off-by: Daniel J Walsh [email protected]

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhatdan

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 [rhatdan]

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

[rhatdan]

@edsantiago PTAL

[edsantiago]

I'll keep my fingers crossed.

I'm seeing a HUGE number of flakes in the podman start --all test, which has nothing to do with pods, so I think there might be two separate issues. This one LGTM though.

[rhatdan]

The --start=all is brand new, so I can take a look tomorrow,

[edsantiago]

I'm not sure it has to do with start --all. My working hypothesis, which I'll start work on tomorrow, is that it has to do with podman rm cid1 cid2 cid3 (a list of multiple CIDs). But it could also be related to rmi of a container that has been restarted. Anyhow, more tomorrow. Thanks for this one.

[edsantiago]

Well, it didn't fix the container-related issue

[rhatdan]

I think my other PR will fix all of them.

[rhatdan]

#10452