-
Notifications
You must be signed in to change notification settings - Fork 30
Fails to cf push
app after a fresh bosh deploy
to AWS eu-west-1
#246
Comments
Thanks for the great issue summary. I'll try to investigate further soon. |
Thank you for your fast response! Today I have tried deploying in us-east-1, this had the same result. Could you give me a pointer on how to debug this problem? I know how I can |
I bumped into the same issue when trying to deploy CF to AWS eu-west-1. The problem was somehow resolved after rebooting the data/0 instance, so this might help in narrowing the problem down a bit. |
Confirm what @antoniou said after rebooting data/0 push works fine |
Same issue for me when deploying CF to AWS ap-southeast-2 (Sydney). I needed to reboot api/0 and data/0 to get it to work. I captured the following cf push -t output of the fail:
The app I was trying to upload had a single text file. My guess is that there is some kind of communication issue between the api/0 node and the data/0 node. |
A more specific "fix" - restarting the cloud_controller on api/0. Specifically
|
I had a similar problem and its the same as described by mrdavidlaing. The cf crash report was identical, the second last status showed the app as running then the last get to the app status shoed the app as failed. Restarting the API controller process did not solve the issue (as suggested by the last post on the issue) but restarting the data node did. Any ideas as to why this problem occurs ? |
No. However, I have figured out a way to trigger the issue on an existing bosh-cloudfoundry (medium) cluster. Just run |
We are running into the same issue. Has anyone made any progress here? |
Same issue with deploying on own Openstack. |
I'll try to create time to upgrade to v166 soon. |
I'm using v141. I tried v166 and v165 but I had problem to deploy it. Can I try another version to deploy Cloud Foundry on Openstack Grizzly? |
interesting, I solved my problem. More here: ravanrijn/styx#13 (comment) |
i came to the same problem, and i check the log file,which is on the node where you deploy the cloud_controller_ng. (/var/vcap/sys/log/cloud_controller_ng/jobs_work.stdout.log), there is error like this [Worker(host:b011166d-1b50-40ff-a5f9-af0fa2426680 pid:1075)] Job AppBitsPackerJob (id=69) FAILED (0 prior attempts) with Errno::EACCES: Permission denied - /var/vcap/nfs/shared, i change the group and owner to vcap, and it works in my situation. |
I have a working EC2 v168 deployment. Hopefully porting into bosh-cf templates soon. On Sun, Apr 20, 2014 at 8:23 AM, linxistar8023 notifications@github.com
|
After a fresh deployment of cloud-foundry to AWS eu-west-1 a
cf push
fails with the following error:Subsequent running
cf start
results in:All the app files are available on instance
api/0
in/var/vcap/shared/cc-resources
.How to reproduce:
bosh show cf attributes
, usecf target http://api.54.246.83.1.xip.io
,cf login
,cf create-org admin
,cf create-space testing
,cf switch-space testing
. To login/setup space.git clone https://github.com/cloudfoundry-community/cf-env.git
andcd cf-env
.cf push
.Push Trace: https://gist.github.com/tader/7a7a073c6e70c6db373e
The text was updated successfully, but these errors were encountered: