Fix printing errors from failed binary runs

I had the kublet die on startup and the only error was "0x401da0" Which I assume is an address of the err.Error function. The other way to fix this, I think, would be to use err.Error(), however that could cause fmt.Fprintf() problems, debuging on the error message people used. Now I get a nice clean error I can understand: "cAdvisor.New() err = mountpoint for cpu not found"

Fix printing errors from failed binary runs
8e7d1419 · Eric Paris · c1943739 · 8e7d1419 · 8e7d1419 · 8e7d1419
Commit 8e7d1419 authored Apr 10, 2015 by Eric Paris
Showing with 4 additions and 4 deletions

apiserver.go cmd/kube-apiserver/apiserver.go +1 -1

controller-manager.go cmd/kube-controller-manager/controller-manager.go +1 -1

proxy.go cmd/kube-proxy/proxy.go +1 -1

kubelet.go cmd/kubelet/kubelet.go +1 -1

No files found.
--- a/cmd/kube-apiserver/apiserver.go
+++ b/cmd/kube-apiserver/apiserver.go
@@ -42,7 +42,7 @@ func main() {
 	verflag.PrintAndExitIfRequested()
 	if err := s.Run(pflag.CommandLine.Args()); err != nil {
-		fmt.Fprint(os.Stderr, err.Error)
+		fmt.Fprint(os.Stderr, "%v\n", err)
 		os.Exit(1)
 	}
 }
--- a/cmd/kube-controller-manager/controller-manager.go
+++ b/cmd/kube-controller-manager/controller-manager.go
@@ -49,7 +49,7 @@ func main() {
 	verflag.PrintAndExitIfRequested()
 	if err := s.Run(pflag.CommandLine.Args()); err != nil {
-		fmt.Fprint(os.Stderr, err.Error)
+		fmt.Fprint(os.Stderr, "%v\n", err)
 		os.Exit(1)
 	}
 }
--- a/cmd/kube-proxy/proxy.go
+++ b/cmd/kube-proxy/proxy.go
@@ -45,7 +45,7 @@ func main() {
 	verflag.PrintAndExitIfRequested()
 	if err := s.Run(pflag.CommandLine.Args()); err != nil {
-		fmt.Fprint(os.Stderr, err.Error)
+		fmt.Fprint(os.Stderr, "%v\n", err)
 		os.Exit(1)
 	}
 }
--- a/cmd/kubelet/kubelet.go
+++ b/cmd/kubelet/kubelet.go
@@ -44,7 +44,7 @@ func main() {
 	verflag.PrintAndExitIfRequested()
 	if err := s.Run(pflag.CommandLine.Args()); err != nil {
-		fmt.Fprint(os.Stderr, err.Error)
+		fmt.Fprint(os.Stderr, "%v\n", err)
 		os.Exit(1)
 	}
 }