Troubleshoot Rolling Update¶
This section helps you identify and resolve some issues that you might encounter when using the rolling update.
The publish result is timeout after the publish completes¶
The publish log shows deployment exceeded its progress deadline.
Cause¶
The timeout shown in the publish result indicates that the publish deployment time exceeds the timeout configured in the deployment stage, which does not mean the publish failed.
Solution¶
To double-check if the application is published successfully:.
Click View Pods operation status to view pod status.
If the pod is
Running, check if the image tag is the same as the image selected in the publish form.
The default timeout is 10 minutes. Contact EnOS technical support to modify the timeout value if you want to prevent publish timeout.
Pod failed during publishing¶
The pod status is failed and the deployment information shows Liveness probe failed or Readiness probe failed.
Cause¶
The publish is not yet complete and the probe ran longer than the timeout period.
Solution¶
View the Pod logs and confirm if the service is starting correctly in the Logs tab.
Click View Pods operation status to go to the Pods list.
Click the Pod name to go to the Pod details page.
Click the Log tab to check if any errors are reported in the log.
If there is no error in the log, extend the liveness probe or readiness probe timeout.
From the left navigation bar, select Container > Deployments.
Click the
icon on the right side of the application to go to the Edit Deployment page and adjust the timeout for the liveness probe or the readiness probe.
