Re: Can't create/update buildpacks, "a filename must be specified"
|
Matthew Sykes <matthew.sykes@...>
You may need to supply your access log from the nginx in front of cc or the
toggle quoted messageShow quoted text
cc log because when I create a new buildpack, it's working just fine: $ CF_TRACE=true cf create-buildpack test-binary-bp ./binary_buildpack-cached-v1.0.1.zip 1 --enable VERSION: 6.11.3-cebadc9 Creating buildpack test-binary-bp... REQUEST: [2015-06-29T20:10:37-04:00] POST /v2/buildpacks?async=true HTTP/1.1 Host: api.10.244.0.34.xip.io Accept: application/json Authorization: [PRIVATE DATA HIDDEN] Content-Type: application/json User-Agent: go-cli 6.11.3-cebadc9 / darwin {"name":"test-binary-bp","position":1,"enabled":true} RESPONSE: [2015-06-29T20:10:37-04:00] HTTP/1.1 201 Created Content-Length: 337 Content-Type: application/json;charset=utf-8 Date: Tue, 30 Jun 2015 00:10:37 GMT Location: /v2/buildpacks/16e73f3c-3980-4603-ba07-8e5b08b78f7b Server: nginx X-Cf-Requestid: 49dc1a83-c37a-4311-66e5-5d2a2aea5df3 X-Content-Type-Options: nosniff X-Vcap-Request-Id: c7ac7b0c-9261-4b2b-7df6-d7788ba26827::168b561c-4e58-4f7c-9bf4-50ac6589522c { "metadata": { "guid": "16e73f3c-3980-4603-ba07-8e5b08b78f7b", "url": "/v2/buildpacks/16e73f3c-3980-4603-ba07-8e5b08b78f7b", "created_at": "2015-06-30T00:10:37Z", "updated_at": null }, "entity": { "name": "test-binary-bp", "position": 1, "enabled": true, "locked": false, "filename": null } } OK Uploading buildpack test-binary-bp... REQUEST: [2015-06-29T20:10:37-04:00] PUT /v2/buildpacks/16e73f3c-3980-4603-ba07-8e5b08b78f7b/bits HTTP/1.1 Host: api.10.244.0.34.xip.io Accept: application/json Authorization: [PRIVATE DATA HIDDEN] Content-Type: multipart/form-data; boundary=a63345d0d8a03bcdf636aed591aa2d57acfe2e910bcc2a3835ed609c270f User-Agent: go-cli 6.11.3-cebadc9 / darwin [MULTIPART/FORM-DATA CONTENT HIDDEN] Done uploading RESPONSE: [2015-06-29T20:10:37-04:00] HTTP/1.1 201 Created Content-Length: 387 Content-Type: application/json;charset=utf-8 Date: Tue, 30 Jun 2015 00:10:37 GMT Server: nginx X-Cf-Requestid: dd6cff31-5d91-4730-6f46-cd6e085bd007 X-Content-Type-Options: nosniff X-Vcap-Request-Id: f5db441f-1293-429a-460a-74eb71cffaeb::c0a244bf-a50b-47d3-b2f1-cbab01a3d22a { "metadata": { "guid": "16e73f3c-3980-4603-ba07-8e5b08b78f7b", "url": "/v2/buildpacks/16e73f3c-3980-4603-ba07-8e5b08b78f7b", "created_at": "2015-06-30T00:10:37Z", "updated_at": "2015-06-30T00:10:37Z" }, "entity": { "name": "test-binary-bp", "position": 1, "enabled": true, "locked": false, "filename": "binary_buildpack-cached-v1.0.1.zip" } } OK ✓ $ cf buildpacks Getting buildpacks... buildpack position enabled locked filename test-binary-bp 1 true false binary_buildpack-cached-v1.0.1.zip staticfile_buildpack 2 true false staticfile_buildpack-cached-v1.2.0.zip java_buildpack 3 true false java-buildpack-v3.0.zip ruby_buildpack 4 true false ruby_buildpack-cached-v1.4.2.zip nodejs_buildpack 5 true false nodejs_buildpack-cached-v1.3.4.zip go_buildpack 6 true false go_buildpack-cached-v1.4.0.zip python_buildpack 7 true false python_buildpack-cached-v1.4.0.zip php_buildpack 8 true false php_buildpack-cached-v3.3.0.zip binary_buildpack 9 true false binary_buildpack-cached-v1.0.1.zip ✓ $ cf --version cf version 6.11.3-cebadc9-2015-05-20T18:59:33+00:00 For buildpacks, nginx handles most of the heavy lifting and then passes modified parameters to the cc for processing. The upload processor then uses the modified params to do the right thing... Are you running a non-standard configuration that doesn't use nginx to frontend cc?
On Mon, Jun 29, 2015 at 3:22 PM, kyle havlovitz <kylehav(a)gmail.com> wrote:
After some more digging I found that it seems to be a problem in --
Matthew Sykes matthew.sykes(a)gmail.com
|
|
|