seeing "Error while getting namespace status, defaulting to off"
bigangryrobot opened this issue · 4 comments
kubectl version
*[master] Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:44:38Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.2", GitCommit:"477efc3cbe6a7effca06bd1452fa356e2201e1ee", GitTreeState:"clean", BuildDate:"2017-04-19T20:22:08Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
logs
2017/05/09 14:13:12 Waiting for directory at /k8s/apps... 2017/05/09 14:13:17 Found directory at /k8s/apps 2017/05/09 14:13:17 Launching webserver 2017/05/09 14:13:22 Most recent commit hash is 54b3c55d0c9cbaaf9636bd3e41cf2a99027a7e3f (previously was ), queueing run. 2017/05/09 14:13:22 Run queued. 2017/05/09 14:13:22 Started apply run at 2017-05-09 14:13:22.739666938 +0000 UTC 2017/05/09 14:13:22 Applying dir /k8s/apps/k8s 2017/05/09 14:13:23 ERROR: Error while getting namespace status, defaulting to off: error=(exit status 1) 2017/05/09 14:13:23 Finished apply run at 2017-05-09 14:13:23.150030607 +0000 UTC 2017/05/09 14:14:17 Full run interval (1m0s) reached, queueing run. 2017/05/09 14:14:17 Run queued. 2017/05/09 14:14:17 Started apply run at 2017-05-09 14:14:17.739580477 +0000 UTC 2017/05/09 14:14:17 Applying dir /k8s/apps/k8s 2017/05/09 14:14:17 ERROR: Error while getting namespace status, defaulting to off: error=(exit status 1) 2017/05/09 14:14:17 Finished apply run at 2017-05-09 14:14:17.974898526 +0000 UTC 2017/05/09 14:15:17 Full run interval (1m0s) reached, queueing run. 2017/05/09 14:15:17 Run queued. 2017/05/09 14:15:17 Started apply run at 2017-05-09 14:15:17.739542303 +0000 UTC 2017/05/09 14:15:22 Applying dir /k8s/apps/k8s 2017/05/09 14:15:24 ERROR: Error while getting namespace status, defaulting to off: error=(exit status 1) 2017/05/09 14:15:24 Finished apply run at 2017-05-09 14:15:24.091099922 +0000 UTC 2017/05/09 14:16:17 Full run interval (1m0s) reached, queueing run. 2017/05/09 14:16:17 Run queued. 2017/05/09 14:16:17 Started apply run at 2017-05-09 14:16:17.73957245 +0000 UTC 2017/05/09 14:16:17 Applying dir /k8s/apps/k8s 2017/05/09 14:16:17 ERROR: Error while getting namespace status, defaulting to off: error=(exit status 1) 2017/05/09 14:16:17 Finished apply run at 2017-05-09 14:16:17.990069064 +0000 UTC 2017/05/09 14:17:17 Full run interval (1m0s) reached, queueing run. 2017/05/09 14:17:17 Run queued. 2017/05/09 14:17:17 Started apply run at 2017-05-09 14:17:17.739536825 +0000 UTC 2017/05/09 14:17:18 Applying dir /k8s/apps/k8s 2017/05/09 14:17:18 ERROR: Error while getting namespace status, defaulting to off: error=(exit status 1) 2017/05/09 14:17:18 Finished apply run at 2017-05-09 14:17:18.260292603 +0000 UTC 2017/05/09 14:18:17 Full run interval (1m0s) reached, queueing run. 2017/05/09 14:18:17 Run queued. 2017/05/09 14:18:17 Started apply run at 2017-05-09 14:18:17.739551918 +0000 UTC 2017/05/09 14:18:17 Applying dir /k8s/apps/k8s 2017/05/09 14:18:17 ERROR: Error while getting namespace status, defaulting to off: error=(exit status 1) 2017/05/09 14:18:17 Finished apply run at 2017-05-09 14:18:17.960552741 +0000 UTC
could this simply be an auth issue between this pod and kube that is not described well in the error?
I'm seeing this trying to reason it out. kube-applier pod running running with service account as cluster-admin so I know it has the proper access to the API.
kube-applier-789446705-1gb19 kube-applier 2017/11/09 16:37:53 Applying dir /k8s/resources/cluster-roles
kube-applier-789446705-1gb19 git-sync I1109 16:37:53.127246 1 main.go:341] no update required
kube-applier-789446705-1gb19 git-sync I1109 16:37:53.127274 1 main.go:167] next sync in 0 seconds
kube-applier-789446705-1gb19 kube-applier 2017/11/09 16:37:53 ERROR: Error while getting namespace status, defaulting to off: error=(exit status 1)
kube-applier-789446705-1gb19 kube-applier 2017/11/09 16:37:53 Finished apply run at 2017-11-09 16:37:53.263653187 +0000 UTC
Sorry I am just getting to this now.
@bobhenkel which version of kube are you running?
I am wondering if this is related to known namespace bugs in earlier 1.5 and 1.6 releases of Kubernetes. 1.5.8+ and 1.6.3+ have the fix.
@bigangryrobot @bobhenkel are you still seeing problems on one of the "supported" versions? (see README)
closing due to inactivity, feel free to reopen if still facing the issue