Re: Can't create/update buildpacks, "a filename must be specified"

kyle havlovitz <kylehav@...>

After some more digging I found that it seems to be a problem in
The 'params' object here is being referenced incorrectly; it contains a key
called 'buildpack' that maps to an object which has a :filename field which
contains the correct buildpack filename, but the code is trying to
reference params['buildpack_name'], which doesn't exist, so it throws an
exception. Changing that above line to say uploaded_filename
= params['buildpack'][:filename] fixed the issue for me. Could this be
caused by my CLI and the cloud controller having out of sync versions? The
api version on the CC is 2.23.0, and tI've been using the 6.11 CLI.

On Mon, Jun 29, 2015 at 9:31 AM, kyle havlovitz <kylehav(a)> wrote:

Here's a gist of the output I get and the command I run:

On Fri, Jun 26, 2015 at 10:58 PM, Matthew Sykes <matthew.sykes(a)>

It should work since our acceptance tests validate this on every build we
cut [1]. Are you running the operation as someone with a cc admin scope?

If you want to create a gist with the log (with secrets redacted) from
running `cf` with CF_TRACE=true, we could certainly take a look.


On Fri, Jun 26, 2015 at 2:36 PM, kyle havlovitz <kylehav(a)>

I'm having an issue where I can't upload any buildpack to cloudfoundry;
it says "The buildpack upload is invalid: a filename must be specified" and
the cf_trace confirms it's sending a null value for filename. The thing is,
I have specified a file name every time and get this error. I've used a few
different CLI versions and uploaded different buildpacks as both zip
files/directories, and nothing works. Is this a bug in the CLI/cloud
controller, or am I doing something wrong?

cf-dev mailing list

Matthew Sykes

cf-dev mailing list

Join to automatically receive all group messages.