GCE kube-up.sh timeout with Trusty distribution

[font]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:57:05Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}

Environment:

• Cloud provider or hardware configuration: GCE
• OS (e.g. from /etc/os-release):

$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="14.04.5 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.5 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

• Kernel (e.g. uname -a):

$ uname -a
Linux kubernetes-minion-group-1rsk 4.4.0-53-generic #74~14.04.1-Ubuntu SMP Fri Dec 2 03:43:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

What happened:
Automated GCE Kubernetes cluster deployment using Ubuntu Trusty image failed to come up properly and timed out with:

Waiting up to 300 seconds for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This may time out if there was some uncaught error during start up.

....................................................................................................................................................Cluster failed to initialize within 300 seconds.

Looking at the logs from a failed node and I see:

Dec 21 20:03:21 kubernetes-minion-group-72n3 kube-env: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found
Dec 21 20:03:21 kubernetes-minion-group-72n3 kube-install-packages: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found
Dec 21 20:03:21 kubernetes-minion-group-72n3 kubelet: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found
Dec 21 20:03:21 kubernetes-minion-group-72n3 kube-install-additional-packages: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found
Dec 21 20:03:21 kubernetes-minion-group-72n3 kube-docker: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found
Dec 21 20:03:21 kubernetes-minion-group-72n3 kernel: [   35.521073] init: kubelet main process ended, respawning
Dec 21 20:03:21 kubernetes-minion-group-72n3 kube-addons: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found
Dec 21 20:03:21 kubernetes-minion-group-72n3 kube-proxy: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found
Dec 21 20:03:31 kubernetes-minion-group-72n3 kubelet: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found
Dec 21 20:03:31 kubernetes-minion-group-72n3 kube-docker: /proc/self/fd/9: 431: /etc/kube-configure-helper.sh: function: not found

What you expected to happen:
Successful deployment of Kubernetes cluster on GCE with Ubuntu Trusty image.

How to reproduce it (as minimally and precisely as possible):

$ curl -sS https://get.k8s.io -o kube.sh
$ export KUBERNETES_RELEASE=v1.5.1
$ export KUBERNETES_PROVIDER=gce
$ export KUBERNETES_SKIP_CREATE_CLUSTER=true
$ bash kube.sh
$ export KUBE_GCE_MASTER_IMAGE=ubuntu-1404-trusty-v20161213
$ export KUBE_GCE_MASTER_PROJECT=ubuntu-os-cloud
$ export KUBE_GCE_NODE_IMAGE=ubuntu-1404-trusty-v20161213
$ export KUBE_GCE_NODE_PROJECT=ubuntu-os-cloud
$ export KUBE_MASTER_OS_DISTRIBUTION=trusty
$ export KUBE_NODE_OS_DISTRIBUTION=trusty
$ cd kubernetes
$ ./cluster/kube-up.sh

Anything else we need to know:
Also, in order to reproduce this you'll need to correct https://github.com/kubernetes/kubernetes/blob/v1.5.1/cluster/gce/trusty/master-helper.sh#L25 and https://github.com/kubernetes/kubernetes/blob/v1.5.1/cluster/gce/trusty/node-helper.sh#L25 to use the ${KUBE_ROOT} variable. See #39129 for more details.

[castrojo]

/sig cluster-lifecycle

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[font]

/close