Status Update
Comments
va...@google.com <va...@google.com>
ku...@google.com <ku...@google.com> #2
Hello,
Thank you for contacting the Google Cloud support team.
I have reviewed your reported issue. I attempted to reproduce the issue by deploying a custom runtime application to the App Engine Flexible environment; specifying only some liveness check settings in the app.yaml, as you mentioned. However, I found that it is working as expected, using the default values for not-specified liveness check settings as specified in the
Nevertheless, if it’s still not working the way you want, it appears to be an issue observed specifically at your end, specific to your project or environment. It would need more specific debugging and analysis. To ensure a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking
Please note that the Issue Tracker is primarily meant for reporting commonly observed issues and requesting new features. For individual support issues, it is best to utilize the support ticketing system. For now, I'm going to close this issue which will no longer be monitored. If you have any additional issues or concerns, please don’t hesitate to create a new issue on the
Thank you!
Description
Problem you have encountered:
The deployment to App Engine Flex fails with error
What you expected to happen:
The deployment to finish correctly, as it did before, using default values for not-speficied liveness check settings as specified inhttps://cloud.google.com/appengine/docs/flexible/reference/app-yaml?tab=custom#liveness_checks
Steps to reproduce:
Deploy custom runtime application to the App Engine Flex and specify following liveness check settings in the app.yaml
Workaround is to specify all the missing fields with their default values: