Downward API volume should provide podname as non-root with fsgroup [Feature:FSGroup] [Volume]

[bparees]

/openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin5_pXiR/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:83
Expected error:
    <*errors.errorString | 0xc4216fac30>: {
        s: "expected pod \"metadata-volume-dcecacd1-5f01-11e7-ba1e-0e66c60935d2\" success: <nil>",
    }
    expected pod "metadata-volume-dcecacd1-5f01-11e7-ba1e-0e66c60935d2" success: <nil>
not to have occurred
/openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin5_pXiR/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:2183

Seen in: https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/1208/

[derekwaynecarr]

a similar issue was here:
kubernetes/kubernetes#42980

it was sourced back to a fix in kubelet panic:
kubernetes/kubernetes#42927

which we have in origin now:
#13653

we need to triage the node logs as it should not be from the original flake upstream why this failed.

[derekwaynecarr]

per discussion with @stevekuznetsov there is no way to access the node log to debug this flake further.

i did review the docker logs and saw nothing of significance.

the node logs in future flakes will be available with openshift-eng/aos-cd-jobs#389

[derekwaynecarr]

the flake happened on gce, and the node logs were not yet avaialble on gce failures...

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[stevekuznetsov]

Doesn't seem like the problem still exists.

/close