Closed johha closed 2 months ago
Honestly I have no idea. It sounds like some sort of caching issue - there are some stale references to the previous directory inside CF. I don't see any hard-coded references to app
or src
inside of this buildpack.
I'd probably proceed by ruling out caching - using a strategy other than rolling
, pushing new apps with a src
directory and trying to revert to app
, picking completely different names for the directories to ensure there's no magic going on, etc.
I'm going to close this out as there's been no response in over a year.
I have a python web application which is pushed with
cf push -f manifest.yml --strategy rolling
. The app has the following structure:Profile
runtime.txt
manifest.yml
This app has been running like this for multiple months. Recently I renamed the
app
directory tosrc
including updating theProcfile
(web: python src/app.py
). I was able to push the app with the changes on multiple foundations BUT on some foundationscf push -f manifest.yml --strategy rolling
failed with errors like:can't open file '/home/vcap/app/./app/app.py': [Errno 2] No such file or directory
can't open file '/home/vcap/app/app/app.py': [Errno 2] No such file or directory
.Obviously the path for
app.py
is wrong and should containsrc
. Unfortunately I wasn't able to reproduce the issue. I could work around the issue by renamingsrc
back toapp
. ¯_(ツ)_/¯Question: Why is the
app.py
path wrong? I could also imagine that this is caused by Diego or CAPI but maybe you have some hints what to look out for.What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version
?