Comment 2 for bug 1845935

Some observations:

in the system journal:
Sep 27 05:57:34 undercloud.localdomain podman[117006]: 2019-09-27 05:57:34.34739525 +0000 UTC m=+1.943270211 container died 5451dfb68fa4509f0f6199d046288a9421ccdd8a82a7ae56865f83f5c4c9447d (image=docker.io/tripleostein/centos-binary-mariadb:current-tripleo, name=mysql)
Sep 27 05:57:39 undercloud.localdomain podman[117163]: 2019-09-27 05:57:39.299614887 +0000 UTC m=+0.190275281 container died 5451dfb68fa4509f0f6199d046288a9421ccdd8a82a7ae56865f83f5c4c9447d (image=docker.io/tripleostein/centos-binary-mariadb:current-tripleo, name=mysql)

in podman inspect:

+ podman inspect mysql
[
    {
        "Id": "5451dfb68fa4509f0f6199d046288a9421ccdd8a82a7ae56865f83f5c4c9447d",
...
        "State": {
            "OciVersion": "1.0.1-dev",
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 117615,
            "ConmonPid": 117591,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2019-09-27T05:57:40.788290976Z",
            "FinishedAt": "2019-09-27T05:57:39.058498867Z",

This shows the failures logged in the journal prepended the normal execution of the container later, and the most recent failure event 2019-09-27 05:57:39.299614887 seems related to that was logged as FinishedAt.

There is also totally a 131 "container died" events had been logged for that example CI job.