You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every line of gce-machine-controller's log ends up having an error message prefix of "ERROR: logging before flag.Parse". This is due to an unfortunate artifact of glog's design. This can be fixed with the hack outlined here: kubernetes/kubernetes#17162.
See below for an example of the log output:
ERROR: logging before flag.Parse: I0523 21:53:41.081142 1 queue.go:38] Start Machine Queue
ERROR: logging before flag.Parse: I0523 21:53:41.081442 1 queue.go:38] Start NodeWatcher Queue
ERROR: logging before flag.Parse: E0523 21:53:41.386480 1 reflector.go:205] sigs.k8s.io/cluster-api/pkg/controller/sharedinformers/zz_generated.api.register.go:56: Failed to list *v1alpha1.MachineDeployment: the server could not find the requested resource (get machinedeployments.cluster.k8s.io)
ERROR: logging before flag.Parse: E0523 21:53:41.386689 1 reflector.go:205] sigs.k8s.io/cluster-api/pkg/controller/sharedinformers/zz_generated.api.register.go:54: Failed to list *v1alpha1.Cluster: the server could not find the requested resource (get clusters.cluster.k8s.io)
ERROR: logging before flag.Parse: E0523 21:53:41.386737 1 reflector.go:205] sigs.k8s.io/cluster-api/pkg/controller/sharedinformers/zz_generated.api.register.go:57: Failed to list *v1alpha1.MachineSet: the server could not find the requested resource (get machinesets.cluster.k8s.io)
ERROR: logging before flag.Parse: E0523 21:53:41.394484 1 reflector.go:205] sigs.k8s.io/cluster-api/pkg/controller/sharedinformers/zz_generated.api.register.go:55: Failed to list *v1alpha1.Machine: the server could not find the requested resource (get machines.cluster.k8s.io)
ERROR: logging before flag.Parse: E0523 21:53:41.411882 1 node.go:59] Error getting machine gce-master-test1: the server could not find the requested resource (get machines.cluster.k8s.io gce-master-test1)
ERROR: logging before flag.Parse: E0523 21:53:41.412028 1 node.go:59] Error getting machine gce-node-msvcv: the server could not find the requested resource (get machines.cluster.k8s.io gce-node-msvcv)
ERROR: logging before flag.Parse: E0523 21:53:41.415440 1 node.go:59] Error getting machine gce-node-lw7t7: the server could not find the requested resource (get machines.cluster.k8s.io gce-node-lw7t7)
The text was updated successfully, but these errors were encountered:
Every line of gce-machine-controller's log ends up having an error message prefix of "ERROR: logging before flag.Parse". This is due to an unfortunate artifact of glog's design. This can be fixed with the hack outlined here: kubernetes/kubernetes#17162.
See below for an example of the log output:
The text was updated successfully, but these errors were encountered: