process valueFrom in build strategy environment variables test context should successfully resolve valueFrom in s2i build environment variables

[0xmichalis]

/tmp/openshift/build-rpm-release/tito/rpmbuild-originsmcihc/BUILD/origin-3.7.0/_output/local/go/src/github.com/openshift/origin/test/extended/builds/valuefrom.go:77
Expected
    <bool>: false
to be true
/tmp/openshift/build-rpm-release/tito/rpmbuild-originsmcihc/BUILD/origin-3.7.0/_output/local/go/src/github.com/openshift/origin/test/extended/builds/valuefrom.go:66

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/16915/test_pull_request_origin_extended_conformance_gce/10226/
/assign bparees
/kind test-flake

[bparees]

Oct 22 19:50:23.636: INFO: 2017-10-22T19:50:17.942748000Z 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-pod3a1c7d43_b762_11e7_8538_42010a8e0002.slice/docker-2ef45289f4558b73fc22ee000087862c4f6b82638d4c4e4c0141b2aee429a945.scope/cgroup.procs: no such file or directory\""

@jwhonce looks like containers team to me.

[bparees]

@Kargakis any reason it's not p1?

[0xmichalis]

No, p1 sgtm if we use it as a means to draw attention.