Windows 64 bit CLI fails at buildpack compile phase when pushing python script.

[strassbm]

While trying to verify I can use Pivotal correctly, I found the following example: https://github.com/michaljemala/hello-python

Ran it like so: cf push -m 128M -b https://github.com/heroku/heroku-buildpack-python.git

It was returning: Server error, status code: 400, error code: 170004, message: App staging failed in the buildpack compile phase.

And: 2014-07-21T12:31:33.00-0600 [STG] OUT ! Requested runtime (python-2.6.5 2014-07-21T12:31:33.00-0600 [STG] OUT ) is not available for this stack (cedar).

I tried it with the other two python build packs mentioned with the same errors. We did the same thing on my friends mac and it worked flawlessly. I think it must be a bug in the CLI.

Thanks.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/75523810.

[drich10]

Hi @strassbm,

What version of the cli are you using? Also, what happens when you try the push without specifying the buildpack? The reason for the latter is because there's a public python buildpack for Cloud Foundry, so you shouldn't have to specify one.

Cheers, @krishicks && @drich10 CF Community Pair

[strassbm]

Hi,

I’m using cli version 6.3.0. I just tried the push using: cf push HelloPy -m 128M and cf push HelloPy

And got: Server error, status code: 400, error code: 170004, message: App staging failed in the buildpack compile phase 2014-07-24T11:41:05.73-0600 [STG] ERR Cloning into '/tmp/buildpacks/heroku-buildpack-python'... 2014-07-24T11:41:06.32-0600 [STG] OUT ----------------------------------- 2014-07-24T11:41:06.32-0600 [STG] OUT BUILD_DIR: 2014-07-24T11:41:06.32-0600 [STG] OUT CACHE_DIR: /tmp/cache 2014-07-24T11:41:06.32-0600 [STG] OUT Python?: /usr/bin/python 2014-07-24T11:41:06.33-0600 [STG] ERR Python 2.6.5

Thanks, Mathew

From: Derek Richard [mailto:notifications@github.com] Sent: Wednesday, July 23, 2014 10:41 AM To: cloudfoundry/cli Cc: Mathew Strassburg Subject: Re: [cli] Windows 64 bit CLI fails at buildpack compile phase when pushing python script. (#220)

Hi @strassbmhttps://github.com/strassbm,

What version of the cli are you using? Also, what happens when you try the push without specifying the buildpack? The reason for the latter is because there's a public python buildpack for Cloud Foundry, so you shouldn't have to specify one.

Cheers, @krishickshttps://github.com/krishicks && @drich10https://github.com/drich10 CF Community Pair

— Reply to this email directly or view it on GitHubhttps://github.com/cloudfoundry/cli/issues/220#issuecomment-49900453.

This electronic communication and any attachments may contain confidential and proprietary information of DigitalGlobe, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received. DigitalGlobe reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives.

[drich10]

@strassbm The -b flag is actually sticky, which means that when you tried to push the app again without the -b flag the old buildpack reference was still being used. Our mistake. Instead, you should pass the name of the standard python buildpack that comes with cf-release:

$ cf push -b python_buildpack

What version of cf-release are you pushing the app to? And have you been able to push any other python apps previously from the Windows client?

Cheers, @krishicks && @drich10 CF Community Pair

[goehmen]

@strassbm I am guessing that the recommendation that the CF Community Pair made on 7/24 resolved your issue. If not, please reopen and we can get to a resolution.