-
Bug
-
Resolution: Done
-
Medium
-
Honolulu Release
cm-container 4.0.0 (based on Cloudify's 20.12.15 image) exits very quickly when it first started through Helm, but then comes up successfully.
Because the successful restart happens very quickly, the logs from the initial failure aren't available. Further investigation is needed. To capture the logs from the initial failure, we probably need to suppress the restart by setting a pod restartPolicy of "Never". It appears this will require changing the chart. The current chart has no explicit setting for "restartPolicy" in the pod spec, so it takes the default value of "Always".
- relates to
-
DCAEGEN2-2581 cm-container does not become ready after pod is recreated
- Closed