Extended.[k8s.io] ConfigMap should be consumable from pods in volume [Conformance] [Volume]

[bparees]

/openshifttmp/openshift/build-rpm-release/tito/rpmbuild-originRdjKmf/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/configmap.go:39
Expected error:
    <*errors.errorString | 0xc4217422a0>: {
        s: "expected pod \"pod-configmaps-6a15e904-598c-11e7-8c20-0ea2fa5297b4\" success: <nil>",
    }
    expected pod "pod-configmaps-6a15e904-598c-11e7-8c20-0ea2fa5297b4" success: <nil>
not to have occurred
/openshifttmp/openshift/build-rpm-release/tito/rpmbuild-originRdjKmf/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:2183

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_gce/3599

[derekwaynecarr]

there was an upstream issue:
kubernetes/kubernetes#42782

which was traced back to a panic in kubelet:
kubernetes/kubernetes#42927

which was picked up in openshift bump here:
#13653

i can't access the logs anymore to see, but i suspect this flaked for a different reason than the more serious panic that was the source of the upstream flake which we have the fix for in openshift.

[0xmichalis]

https://ci.openshift.redhat.com/jenkins/view/All/job/merge_pull_request_origin/1350/

[smarterclayton]

https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/test_branch_origin_extended_conformance_gce/1186/

[smarterclayton]

       s: "expected pod \"pod-projected-configmaps-e8a3e259-8b66-11e7-86e3-0ee7704fd4f6\" success: pod \"pod-projected-configmaps-e8a3e259-8b66-11e7-86e3-0ee7704fd4f6\" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2017-08-27 16:32:56 -0400 EDT Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2017-08-27 16:32:56 -0400 EDT Reason:ContainersNotReady Message:containers with unready status: [projected-configmap-volume-test]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2017-08-27 16:32:56 -0400 EDT Reason: Message:}] Message: Reason: HostIP:10.128.0.3 PodIP:172.16.2.76 StartTime:2017-08-27 16:32:56 -0400 EDT InitContainerStatuses:[] ContainerStatuses:[{Name:projected-configmap-volume-test State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:128,Signal:0,Reason:ContainerCannotRun,Message:invalid header field value \"oci runtime error: container_linux.go:247: starting container process caused \\\"process_linux.go:258: applying cgroup configuration for process caused \\\\\\\"open /sys/fs/cgroup/pids/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pode8a8b664_8b66_11e7_92c8_42010a800005.slice/docker-e76f1ade3e27961339a1c690a22206caef83fd163de02ca009e16ceed0861e1f.scope/cgroup.procs: no such file or directory\\\\\\\"\\\"\\n\",StartedAt:2017-08-27 16:32:57 -0400 EDT,FinishedAt:2017-08-27 16:32:57 -0400 EDT,ContainerID:docker://e76f1ade3e27961339a1c690a22206caef83fd163de02ca009e16ceed0861e1f,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:gcr.io/google_containers/mounttest:0.8 ImageID:docker-pullable://gcr.io/google_containers/mounttest@sha256:bec3122ddcf8bd999e44e46e096659f31241d09f5236bc3dc212ea584ca06856 ContainerID:docker://e76f1ade3e27961339a1c690a22206caef83fd163de02ca009e16ceed0861e1f}] QOSClass:BestEffort}",

Looks like a cgroup race, probably new (I think the old one is fixed). Repurposing and bumping priority.

@sjenning (you should add a sig-node group so we can start mentioning that).

[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

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close