Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

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

Kubernetes version (use kubectl version):

v1.3.7

Environment:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release): centOS 7

Kernel (e.g. uname -a):Linux zhouzong-1-e426f249-e94c-439d-a300-ae836e93dada 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Install tools:

Others:

What happened:

1.After running : /home/cmcc/k8s_1.3.7/cluster/images/hyperkube/make build VERSION=v1.3.7,the error below happened.

cp ../../../_output/dockerized/bin/linux/amd64/hyperkube /tmp/tmp.HzRR8SYT3E

cp: cannot stat ‘../../../_output/dockerized/bin/linux/amd64/hyperkube’: No such file or directory

make: *** [build] Error 1

2.According to README, "# First, build the binaries:$ build/run.sh hack/build-cross.sh", after running" build/run.sh: No such file or directory" " hack/build-cross.sh: No such file or directory"

What you expected to happen:

the necessary files for building images should be tarred together. we suggest you do it first.

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

always happen when you build the hypercube image.

Anything else do we need to know:

Issue 2:
Ran into a flaky test

--- FAIL: TestSyncPodsDoesNothing (0.00 seconds)
kubelet_test.go:57: expected []string{"list"}, got []string{"list", "list", "inspect_container", "inspect_container"}
I1028 22:40:10.479932 00811 docker.go:304] Docker Container: foo is not managed by kubelet.
E1028 22:40:10.480297 00811 kubelet.go:641] Unable to get pod with name bar.new.test and uuid info, health checks may be invalid
E1028 22:40:10.480548 00811 kubelet.go:641] Unable to get pod with name foo.new.test and uuid info, health checks may be invalid
E1028 22:40:10.480865 00811 kubelet.go:641] Unable to get pod with name foo.new.test and uuid info, health checks may be invalid
W1028 22:40:10.481460 00811 kubelet.go:337] Unknown protocol '': defaulting to TCP
W1028 22:40:10.481494 00811 kubelet.go:337] Unknown protocol 'foobar': defaulting to TCP
W1028 22:40:10.481721 00811 kubelet.go:901] Pod ..: HostPort is already allocated, ignoring: [[0].port: duplicate value '81']
E1028 22:40:10.483264 00811 kubelet.go:415] Invalid handler: &{<nil> <nil>}
E1028 22:40:10.483415 00811 kubelet.go:641] Unable to get pod with name foo.new.test and uuid info, health checks may be invalid
E1028 22:40:10.483619 00811 kubelet.go:747] Error running pod foo.new.test container bar: failed to call event handler: test error
I1028 22:40:10.484245 00811 runonce.go:62] waiting for 1 pods
I1028 22:40:10.484334 00811 runonce.go:138] container "bar" not found
I1028 22:40:10.484365 00811 runonce.go:112] pod "foo" containers not running: syncing
E1028 22:40:10.484561 00811 kubelet.go:641] Unable to get pod with name foo.new.test and uuid info, health checks may be invalid
I1028 22:40:10.484726 00811 runonce.go:124] pod "foo" containers synced, waiting for 1s
I1028 22:40:11.485208 00811 runonce.go:108] pod "foo" containers running
I1028 22:40:11.485265 00811 runonce.go:75] started pod "foo"
I1028 22:40:11.485303 00811 runonce.go:84] 1 pods started
2014/10/28 22:40:11 http: WriteHeader called with both Transfer-Encoding of "chunked" and a Content-Length of 0
2014/10/28 22:40:11 http: WriteHeader called with both Transfer-Encoding of "chunked" and a Content-Length of 0
2014/10/28 22:40:11 http: WriteHeader called with both Transfer-Encoding of "chunked" and a Content-Length of 0
FAIL
coverage: 68.7% of statements
FAIL github.com/GoogleCloudPlatform/kubernetes/pkg/kubelet 1.542s