extended conformance install downward api failure

[gabemontero]

From https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17480/test_pull_request_origin_extended_conformance_install/3130/

or https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install/3130/consoleFull

[k8s.io] Downward API volume
/tmp/openshift/shell/rpm/BUILD/origin-3.8.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:666
  should update annotations on modification [Conformance] [sig-storage] [Suite:openshift/conformance/parallel] [Suite:k8s] [It]
  /tmp/openshift/shell/rpm/BUILD/origin-3.8.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:154

  Timed out after 120.001s.
  Expected

<did not copy / paste the log data >

to contain substring
    <string>: builder="foo"
    
/tmp/openshift/shell/rpm/BUILD/origin-3.8.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:153

I found no errors for the downwardapi_volume pod in question in the node logs. Nor could I find anything amiss in the master logs around the REST invocations for that pod.

[0xmichalis]

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17516/test_pull_request_origin_extended_conformance_install/3219/

[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