Skip to content
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.

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

Include commands to copy ipamd and plugin logs in from the bottlerocket based EKS worker nodes #1313

Closed
nmour77 opened this issue Feb 9, 2021 · 0 comments · Fixed by #1327
Assignees
Labels
type/enhancement New feature or request

Comments

@nmour77
Copy link

nmour77 commented Feb 9, 2021

What I'd like:
Currently EKS related logs are being collected from bottle rocket AMI based EKS worker nodes by running logdog command from root shell in the Bottlerocket host's root filesystem. However, the below logs are not included in the logs collected by the logdog command.

  • ipamd.log
  • plugin.log

These logs are present in /var/log/aws-routed-eni/ directory when you drop into root shell in the Bottlerocket host's root filesystem by running sudo sheltie

Can you please include the below line in https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/logdog/conf/logdog.common.conf to help us eliminate the manual steps we are following currently.

exec ipamd.log cat /var/log/aws-routed-eni/ipamd.log

exec plugin.log cat /var/log/aws-routed-eni/plugin.log

Any alternatives you've considered:

Currently we are collecting all the required logs using the procedure at aws/amazon-vpc-cni-k8s#1316 (comment). However, we want to automate this so that the manual steps are eliminated.

@jhaynes jhaynes added status/needs-triage Pending triage or re-evaluation type/enhancement New feature or request labels Feb 10, 2021
@gregdek gregdek added priority/p1 and removed status/needs-triage Pending triage or re-evaluation labels Feb 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants