Description of problem: oc commands such as oc get/edit etc can not work in Windows 10 (not sure if Win 8 reproduces; not tested on it yet) oc 3.5 cmds VS openshift 3.5 can work (i.e. not stuck). But checked oc 3.5 cmds with --loglevel 6, it also shows the repeated messages "failed to write cache to C:\Users\star\.kube\... not supported by windows" Version-Release number of selected component (if applicable): oc/openshift v3.6.77 kubernetes v1.6.1+5115d708d7 features: Basic-Auth How reproducible: Always Steps to Reproduce: 1. Prepare project and resources via Linux oc. Download Windows oc. Below do the operations in Windows 2. oc login to master, and try: oc version oc whoami 3. Try others: oc get pod oc edit dc database oc delete svc database oc status 4. Check oc cmds with --loglevel 6 Actual results: 2. These cmds can work 3. These cmds are stuck till Ctrl + C 4. `oc get pod --loglevel 6` shows: I0518 16:51:45.741762 4196 loader.go:354] Config loaded from file C:\Users\star/.kube/config I0518 16:51:47.264013 4196 round_trippers.go:405] GET https://$master:8443/api 200 OK in 1503 milliseconds I0518 16:51:47.557462 4196 round_trippers.go:405] GET https://$master:8443/apis 200 OK in 293 milliseconds I0518 16:51:47.561501 4196 cached_discovery.go:134] failed to write cache to C:\Users\star\.kube\$master_cluster\servergroups.json due to chmod C:\Users\star\.kube\$master_cluster\servergroups.json.689571775: not supported by windows I0518 16:51:47.853778 4196 round_trippers.go:405] GET https://$master:8443/apis/authentication.k8s.io/v1 200 OK in 292 milliseconds I0518 16:51:47.855788 4196 cached_discovery.go:87] failed to write cache to C:\Users\star\.kube\$master_cluster\authentication.k8s.io\v1\serverresources.json due to chmod C:\Users\star\.kube\$master_cluster\authentication.k8s.io\v1\serverresources.json.937666578: not supported by windows I0518 16:51:48.153001 4196 round_trippers.go:405] GET https://$master:8443/apis/authentication.k8s.io/v1beta1 200 OK in 296 milliseconds I0518 16:51:48.156011 4196 cached_discovery.go:87] failed to write cache to C:\Users\star\.kube\$master_cluster\authentication.k8s.io\v1beta1\serverresources.json due to chmod C:\Users\star\.kube\$master_cluster\authentication.k8s.io\v1beta1\serverresources.json.668620361: not supported by windows I0518 16:51:48.451321 4196 round_trippers.go:405] GET https://$master:8443/apis/authorization.k8s.io/v1 200 OK in 294 milliseconds I0518 16:51:48.454333 4196 cached_discovery.go:87] failed to write cache to C:\Users\star\.kube\$master_cluster\authorization.k8s.io\v1\serverresources.json due to chmod C:\Users\star\.kube\$master_cluster\authorization.k8s.io\v1\serverresources.json.293755668: not supported by windows I0518 16:51:48.763595 4196 round_trippers.go:405] GET https://$master:8443/apis/authorization.k8s.io/v1beta1 200 OK in 309 milliseconds I0518 16:51:48.766604 4196 cached_discovery.go:87] failed to write cache to C:\Users\star\.kube\$master_cluster\authorization.k8s.io\v1beta1\serverresources.json due to chmod C:\Users\star\.kube\$master_cluster\authorization.k8s.io\v1beta1\serverresources.json.489402723: not supported by windows I0518 16:51:49.059270 4196 round_trippers.go:405] GET https://$master:8443/apis/autoscaling/v1 200 OK in 292 milliseconds I0518 16:51:49.062284 4196 cached_discovery.go:87] failed to write cache to C:\Users\star\.kube\$master_cluster\autoscaling\v1\serverresources.json due to chmod C:\Users\star\.kube\$master_cluster\autoscaling\v1\serverresources.json.137875302: not supported by windows ... many such messages ... Expected results: 3 and 4: these cmds should work in Windows Additional info:
Pull request is https://github.com/openshift/origin/pull/14399
Verified in oc/openshift v3.6.94, commands oc get/edit etc can work in Windows, not stuck now. As in comment 0: > oc 3.5 cmds VS openshift 3.5 can work (i.e. not stuck). But checked oc 3.5 cmds with --loglevel 6, it also shows the repeated messages "failed to write cache to C:\Users\star\.kube\... not supported by windows" Seems it is worth to backport 3.5 to remove the repeated messages, WDYT about the backport? Thank you
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1716