Community
Participate
Working Groups
When an application is starting and shows as STARTING in Servers view, if user manually refresh the application, the STARTING state is removed. When the application successfully starts, then the app state is correctly set to STARTED. The issue is that the refresh operations triggered manually do not take into account Starting state. If no refresh is performed during starting, then app correctly stays in STARTING until it is started, or operation is canceled, or app is stopped, as expected.
Fix pushed to master. Now refresh operations honour the Starting state of an application. Required changes to CloudFoundryServer, therefore it requires thorough testing to check for regressions.
Verified the fix on 1.0.M3