8000 Curator pod/jobs does not show any logs if there is any syntactical errors in config file · Issue #1543 · elastic/curator · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Curator pod/jobs does not show any logs if there is any syntactical errors in config file #1543

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
prashant407 opened this issue May 8, 202 8000 0 · 2 comments
Open

Curator pod/jobs does not show any logs if there is any syntactical errors in config file #1543

prashant407 opened this issue May 8, 2020 · 2 comments

Comments

@prashant407
Copy link
prashant407 commented May 8, 2020 •
edited
Loading

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

  1. Change some indentation of any parameter in the curator config
  2. Deploy the curator chart.
  3. Check the curator pod logs and Job status of curator.

Specifications

  • Version: 5.8.1
  • Platform: Kubernetes

Context

If there is any syntactical errors in config while deploying the curator then it should through some error message or some logs.
@DaveyDevOps
Copy link

Is this related to
Curator failing silently with invalid yaml #1504
lack of bad yaml feedback?

@untergeek
Copy link
Member

@DaveyDevOps almost certainly, because:

  1. Change some indentation of any parameter in the curator config

implies that very thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@untergeek @DaveyDevOps @prashant407
0