Clarity and Serenity Pods in CrashLoopBackOff due to OOMKilled
PreviousIP-Reconciler Skips Next Pods if it Fails to Add IP to a Pod from the ListNextSelf-Service users not able to view PVCs in the WebUI
Last updated
Clarity and Serenity pods in the airctl-1 namespace on Platform9 Self Managed Cloud Platform [SMCP] environments have CrashLoopBackOff state and the describe outputs of these pods display the reason of termination as OOMKilled.
Platform9 Self Managed Cloud Platform - v5.9.0.
This is a known issue and is resolved in the SMCP v5.9.1 patch.
For more details regarding the bug, please open a support ticket mentioning the JIRA ID: AIR-1236
Last updated