Closed stephanme closed 4 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/161835286
The labels on this github issue will be updated when the story is started.
Hi @stephanme
Does this happen if you repeat the exact same curl -X PUT...
command? If the cloud controller detected that one or more sensitive fields on the process object have changed, it will assign a new version to the process and you'll see momentary outage, but the app should start up again on its own.
BTW, if this is the case, we are working on a way to prevent that type of outage, for the v3 API.
Regards, @ericpromislow CAPI Community Pair (soloing)
Hi @ericpromislow,
the application goes down after a single curl -X PUT ...
. There is no need to repeat the command.
The application does not recover from this outage. It remains stopped and cf apps
shows it in requested state 'started' with '0/1' instances (see also above in section 'Current result'). I have to run a cf restart staticfile-test
manually to get it running again (and this restart results actually in a re-stage).
Best regards, Stephan
Changing the ports of a v2 app will cause it to synchronously restart. This is improved with v3 deployments. Closing due to age.
Issue
results in stopping the application (which was running before). Note that I don't change the application state.
Context
cf-deployment 3.6 capi-release 1.66.0
Any running application, e.g. a simple hello-world style app using the staticfile buildpack.
App configuration:
The problem was detected when trying to scale out an app using a cloud foundry terraform provider. Scaling out with "cf scale -i" works as expected.
Steps to Reproduce
Call PUT /v2/apps/61a0c24d-cb6d-42f4-b4a3-2e2c7ef4b988 with a set of parameters. The parameters don't change the app configuration at all (compare with the GET above).
Expected result
Ideally a 200 without any side effects because the PUT doesn't change anything on the app configuration. Worst case a 200 with an application restart.
In any case, the application shall be (eventually) running.
Current result
The PUT call is executed successfully:
However, the application instance is stopped:
The application is then in a strange state:
The application seems to be in STARTED state even though there is no instance running anymore. A "cf restart" results in restaging the application.