+++ This bug was initially created as a clone of Bug #1541914 +++ Description of problem: Below warning appears if try to set --no-cache for source build # oc start-build ruby-ex --no-cache=false Unable to connect to the server: unexpected EOF; some request body already written Version-Release number of selected component (if applicable): oc v3.9.0-0.36.0 kubernetes v1.9.1+a0ce1bc657 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: always Steps to Reproduce: 1.oc new-app ruby~https://github.com/openshift/ruby-ex 2.oc start-build ruby-ex --no-cache=false 3. Actual results: # oc start-build ruby-ex --no-cache=false Unable to connect to the server: unexpected EOF; some request body already written Expected results: Should warn --no-cache only work for docker build. Additional info: --- Additional comment from Ben Parees on 2018-02-05 16:59:45 EST --- this actually crashes my master api server, so raising severity. --- Additional comment from Ben Parees on 2018-02-05 17:13:01 EST --- pr: https://github.com/openshift/origin/pull/18461
https://github.com/openshift/ose/pull/1051
Verified with below expected result: [root@host-172-16-120-119 ~]# oc start-build ruby-ex --no-cache=false Error from server (BadRequest): Cannot specify Docker build specific options on default/ruby-ex, not a Docker build. [root@host-172-16-120-119 ~]# oc version oc v3.7.29 kubernetes v1.7.6+a08f5eeb62 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://172.16.120.119:8443 openshift v3.7.29 kubernetes v1.7.6+a08f5eeb62 [root@host-172-16-120-119 ~]# openshift version openshift v3.7.29 kubernetes v1.7.6+a08f5eeb62 etcd 3.2.8
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/RHBA-2018:0636