Pod age is shown as <invalid> by oc client

Issue

Pod AGE column shows invalid rather than showing pod age. This can happen when in ContainerCreating or Terminating status:

root@jump-node: ~ # oc get pods --all-namespaces -o wide
NAMESPACE                                  NAME                        READY     STATUS              RESTARTS   AGE         IP             NODE
default                                    docker-registry-3-h3r8g     1/1       Running             0          9d          10.128.9.4     10.10.0.14
default                                    registry-console-1-jrwn7    1/1       Running             0          9d          10.128.8.2     10.10.0.17
default                                    router-1-hqyvp              1/1       Running             5          9d          10.10.0.16     10.10.0.16
default                                    router-1-ybfvx              1/1       Running             1          9d          10.10.0.14     10.10.0.14
extended-test-cli-deployment-gool9-s9abj   readiness-1-deploy          1/1       Running             0          16s         10.129.229.9   10.10.2.67
extended-test-cli-deployment-gool9-s9abj   readiness-1-y831m           0/1       ContainerCreating   0          <invalid>   <none>         10.10.2.65
vlaad27                                    buildconfig0-1-build        0/1       Terminating         0          8d          10.128.245.5   10.10.1.108
vlaad3                                     deploymentconfig1-1-md8ou   0/1       Terminating         0          8d          <none>         10.10.0.170
root@jump-node: ~ # oc get pods --all-namespaces -o wide
NAMESPACE                                  NAME                        READY     STATUS              RESTARTS   AGE       IP             NODE
default                                    docker-registry-3-h3r8g     1/1       Running             0          9d        10.128.9.4     10.10.0.14
default                                    registry-console-1-jrwn7    1/1       Running             0          9d        10.128.8.2     10.10.0.17
default                                    router-1-hqyvp              1/1       Running             5          9d        10.10.0.16     10.10.0.16
default                                    router-1-ybfvx              1/1       Running             1          9d        10.10.0.14     10.10.0.14
extended-test-cli-deployment-gool9-s9abj   readiness-1-deploy          1/1       Running             0          17s       10.129.229.9   10.10.2.67
extended-test-cli-deployment-gool9-s9abj   readiness-1-y831m           0/1       ContainerCreating   0          0s        <none>         10.10.2.65
vlaad27                                    buildconfig0-1-build        0/1       Terminating         0          8d        10.128.245.5   10.10.1.108
vlaad3                                     deploymentconfig1-1-md8ou   0/1       Terminating         0          8d        <none>         10.10.0.170

This can also happen with pods in Running status, as observed in 3.11:

logging-kibana-4-xxxxx                     2/2       Running     0          <invalid>   10.0.0.1
logging-kibana-4-xxxxx                     2/2       Running     0          <invalid>
heketi-storage-1-xxxxx                     1/1       Running     0          <invalid>   10.0.0.1
heketi-storage-1-xxxxx                     1/1       Running     0          <invalid>
heketi-storage-1-xxxxx                     1/1       Running     0          <invalid>   10.0.0.1
logging-es-data-master-xxxxxxxx-8-xxxxx    2/2       Running     0          <invalid>   10.0.0.1
logging-es-data-master-xxxxxxxx-8-xxxxx    2/2       Running     0          <invalid>
docs-1196-xxxxx                            2/2       Running     0          <invalid>   10.0.0.1

This bug has been observed in OCP 3.4 and 3.11.