Description of problem: Docker binary build fails with unrecognized type: *transport.debuggingRoundTripper when master --loglevel=10 Version-Release number of selected component (if applicable): openshift v3.3.1.14 How reproducible: Always Steps to Reproduce: 1. Modify --loglevel=10 in /etc/sysconfig/atomic-openshift-master* and restart master 2. mkdir work; cd work; 3. echo "FROM rhel7" > Dockerfile 4. oc new-build --strategy=docker --binary=true --name=rhel 5. oc start-build rhel --from-dir=. --build-loglevel=10 --loglevel=10 Actual results: $ oc start-build rhel --from-dir=. --build-loglevel=10 --loglevel=10 I0410 23:51:18.124731 4416 helpers.go:172] server response object: [{ "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "Internal error occurred: unable to connect to node, unrecognized type: *transport.debuggingRoundTripper", "reason": "InternalError", "details": { "causes": [ { "message": "unable to connect to node, unrecognized type: *transport.debuggingRoundTripper" } ] }, "code": 500 }] Expected results: Build success Additional info:
does a build pod show up and indicate it is running? are you able to oc rsh to other pods on the same node as the build pod, from the client where you ran oc start-build?
My understanding (thanks to Eric) is that this only happens w/ loglevel 10, thus the severity reduction.
https://github.com/openshift/origin/blob/master/pkg/build/registry/buildconfiginstantiate/rest.go#L233 should be using a kube helper to get the TLSClientConfig instead of casting. (thanks andy).
helper method: https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/pkg/util/net/http.go#L141
https://github.com/openshift/origin/pull/13790
This has been merged into ocp and is in OCP v3.6.39 or newer.
Verified with below version: openshift v3.6.39 kubernetes v1.5.2+43a9be4 etcd 3.1.0 No such error when set loglevel to 10 in masterconfig: $ oc start-build rhel --from-dir=. --build-loglevel=10 --loglevel=10 I0420 14:58:37.436842 32709 loader.go:354] Config loaded from file /home/wzheng/.kube/config I0420 14:58:37.438026 32709 cached_discovery.go:112] returning cached discovery info from /home/wzheng/.kube/host_8_174_59.host.centralci.eng.rdu2.redhat.com_8443/servergroups.json WARNING: Specifying environment variables with binary builds is not supported. I0420 14:58:37.438627 32709 repository.go:367] Executing git show --quiet HEAD --format=%H%n%an%n%ae%n%cn%n%ce%n%B I0420 14:58:37.440321 32709 repository.go:427] Error executing command: exit status 128 I0420 14:58:37.440363 32709 startbuild.go:539] Unable to read Git info from ".": fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). Uploading directory "." as binary input for the build ... I0420 14:58:37.440452 32709 tar.go:200] Adding "/home/wzheng/test/work" to tar ... I0420 14:58:37.440514 32709 tar.go:286] Adding to tar: /home/wzheng/test/work/Dockerfile as Dockerfile WARNING: the provided file may not be an archive (tar, tar.gz, or zip), use --from-file to prevent extraction >>>>>>>>>>>>>>>>>>>>>>> I0420 14:58:41.205689 32709 round_trippers.go:324] Response Headers: I0420 14:58:41.205700 32709 round_trippers.go:327] Date: Thu, 20 Apr 2017 06:58:40 GMT I0420 14:58:41.205709 32709 round_trippers.go:327] Cache-Control: no-store I0420 14:58:41.205716 32709 round_trippers.go:327] Content-Type: application/json I0420 14:58:41.205724 32709 round_trippers.go:327] Content-Length: 1160 I0420 14:58:41.206640 32709 request.go:905] Response Body: {"kind":"Build","apiVersion":"v1","metadata":{"name":"rhel-1","namespace":"wzheng2","selfLink":"/oapi/v1/namespaces/wzheng2/builds/rhel-1","uid":"c811bfb8-2596-11e7-97bf-fa163e3e33f5","resourceVersion":"2558","creationTimestamp":"2017-04-20T06:58:39Z","labels":{"build":"rhel","buildconfig":"rhel","openshift.io/build-config.name":"rhel","openshift.io/build.start-policy":"Serial"},"annotations":{"openshift.io/build-config.name":"rhel","openshift.io/build.number":"1","openshift.io/build.pod-name":"rhel-1-build"},"ownerReferences":[{"apiVersion":"v1","kind":"BuildConfig","name":"rhel","uid":"c2efb4fe-2596-11e7-97bf-fa163e3e33f5"}]},"spec":{"serviceAccount":"builder","source":{"type":"Binary","binary":{}},"strategy":{"type":"Docker","dockerStrategy":{}},"output":{"to":{"kind":"ImageStreamTag","name":"rhel:latest"},"pushSecret":{"name":"builder-dockercfg-tl17b"}},"resources":{},"postCommit":{},"nodeSelector":null,"triggeredBy":null},"status":{"phase":"Running","startTimestamp":"2017-04-20T06:58:40Z","outputDockerImageReference":"172.30.206.9:5000/wzheng2/rhel:latest","config":{"kind":"BuildConfig","namespace":"wzheng2","name":"rhel"},"output":{}}} >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> build "rhel-1" started
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