New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cfPush on the Gradle plugin gets a 500 internal server error #222
Comments
|
@rduncan This appears to only be happening on Pivotal Web Services. We are checking to see what has changed that might be causing this error. |
|
This has been identified as an issue with the Cloud Foundry Cloud Controller on Pivotal Web Services. That issue is being tracked here: https://www.pivotaltracker.com/story/show/80319590. |
|
@scottfrederick |
|
Looking at the pivotaltracker story, this should be fixed now. |
|
@bclozel The code is fixed and pushed to cf-release, not sure it has made its way to PWS prod yet. |
|
Closing this, feel free to re-open if you still see the problem on PWS. |
|
@scottfrederick - confirmed cfPush working as expected! |
|
Great, thanks @rduncan! |
This commit upgrades the version of the Java client used by the buildpack system tests. The upgrade fixes several problems including a HTTP issue and should result in much more stable system test runs. See: cloudfoundry/cf-java-client#222 https://www.pivotaltracker.com/n/projects/816799/stories/78116662 [#79112530]
I have been using the gradle plugin for about a month now and today I am getting a 500 internal server error when the plugin appears requesting the server to return a staging log. The exact error message appears below:
GET request for "https://94fc8ca1665342ffb5414870ef3741ab.run.pivotal.io/staging_tasks/3b62e897189e4343990eda0c62871049/file_path?hmac=995179d429c2cfeb5092b923db620fc296da4ea4bccdb748568953368f980d280fad3a4cadb4b313bc0d4132fcce5cb80bbaa0294a622ba8114cc110a3866068&path=/tmp/staged/logs/staging_task.log×tamp=1412701609&tail&tail_offset=0" resulted in 500 (Internal Server Error); invoking error handler
The text was updated successfully, but these errors were encountered: