Open prashant407 opened 4 years ago
Is this related to Curator failing silently with invalid yaml #1504 lack of bad yaml feedback?
@DaveyDevOps almost certainly, because:
- Change some indentation of any parameter in the curator config
implies that very thing.
No logs appear in curator pods/jobs
Hi,
We are using Curator in Kubernetes platform. If in curator config there is indentation issue, curator pod does not show any logs. Even after using DEBUG mode there are no logs in curator pods.
Expected Behavior
If there is any issue with the indentation in that case curator pod should display some logs.
Actual Behavior
If there is any issue with the indentation then there are no logs in the curator pod.
abc-curator-1588941960 1/1 6s 4m35s abc-curator-1588942080 1/1 5s 2m34s abc-curator-1588942200 1/1 6s 34s
[root@vm-XX-XX-XX-XX abc]# kubectl logs abc-curator-1588941720-fqnnc -n abc [root@vm-XX-XX-XX-XX abc]#
Steps to Reproduce the Problem
Specifications
Context
If there is any syntactical errors in config while deploying the curator then it should through some error message or some logs.