How to resolve unsuccessful deployment to Liferay SaaS EXT environment due to liveness probe failure
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- While deploying a Client Extension to the Liferay SaaS EXT environment, the custom deployment keeps bootlooping with an error indicating Container <service-name> failed liveness probe, will be restarted
Environment
- Liferay SaaS EXT environment
Resolution
- In this particular case, the livenessProbe values in LCP.json might not be adequate for the Client Extension's deployment. The liveness probe is a feature in Liferay Cloud's self-healing functionality that ensures that a service is operation. However, in the case of custom deployments, it may be necessary to adjust the values and increase the livenessProbe value to ensure that it is not erroneously terminated and restarted.
- In certain cases, the readinessProbe values may need to be adjusted, to ensure that the service is responsive.
Did this article resolve your issue ?