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

containerLogManager#compressLog may leave compressed log behind #89489

Open
tedyu opened this issue Mar 25, 2020 · 1 comment
Open

containerLogManager#compressLog may leave compressed log behind #89489

tedyu opened this issue Mar 25, 2020 · 1 comment

Comments

@tedyu
Copy link
Contributor

@tedyu tedyu commented Mar 25, 2020

What happened:
If renaming tmpLog to compressedLog succeeds but log removal fails, the compressedLog may be left behind.

What you expected to happen:
compressedLog should be removed if deletion of the normal log file fails.

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Network plugin and version (if this is a network-related bug):
  • Others:
@tedyu tedyu added the kind/bug label Mar 25, 2020
@tedyu

This comment has been minimized.

Copy link
Contributor Author

@tedyu tedyu commented Mar 25, 2020

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node and removed needs-sig labels Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.